Hi guys I did upgrade from 2.13 to 2.14 and once I did I received the following error:
"
Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.
"
So I uploaded the repair_settings.php file to se what is going on and everything appears to be correct.
Then, I created a file, called test.php with the following code:
<?php
require('Settings.php');
mysql_connect($db_server, $db_user, $db_pass) or die(mysql_error());
mysql_select_db($db_name) or die(mysql_error());
?>
uploaded it to the forum's folder and went to the test.php...
What I received was the following:
Warning: mysql_connect(): Access denied for user '(username)'@'localhost' (using password: NO) in /home/(url to forum)/forum/test.php on line 5
Access denied for user '(username)'@'localhost' (using password: NO)
From what I understand it has something to do with something that the update changed in the database or something...
Can somebody assist me here?
Highly appreciated and I thank you in advance...
That error means your username/password for that mySQL database isnt valid. Have you checked the db credentials at your host's control panel?
Hi,
what you suggested is what I understood as well but everything appears correct.
Frankly, I do not get it...
OK, I checked everything... and everything is OK...
But still the problem remains... and obviously I cannot access the admin panel of the forum...
Is there a way to revert back to the 2.13 version?
Did you take a backup before installing the patch?
If so.. restore that.
If not.., shame on you. Remember to do it next time and EVERY TIME you install any mod
You can try manually undoing the code changes...
HI Kindred, thanks for the way (or should I say Ironic way you did reply, lol)... yes I did take a backup... ;)
Let me try to do the changes manually and I will get back to you in due time
You might want to ask your host for help with that error :) See if they know what goes wrong
OK, here is the update of my issue.
I re-uploaded my forum-backup files and the forum is back to normal.
With only one exception... the shoutbox from my ADK portal does not work anymore...
what I get is:
Parse error: syntax error, unexpected 'if' (T_IF) in /home/......./adkportal/blocks/adk_shoutbox.php on line 1
and while I tried to uninstall the "SMF 2.0.14 Update" I get the following:
This package cannot be uninstalled, because there is no uninstaller!
Please contact the mod author for more information.
Consequently, I had to "take down" the shoutbox until I can resolve the matter or if anyone has experienced and solved the matter with the shoutbox he or she could assists me with solving the problem.? Would be Highly appreciated :)
I do not get why but for a patch that is supposed to upgrade something to cause so many problems, why? I think I am gonna stay away from that specific update :)
Hello,
I have exactly the same problem. I restored the backup and my forum is working now, but still would like to know what causes the error:
"Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later."
Also, I can't seem to gather any logs with more details about what's wrong.
My setup: CentOS 7, Nginx, php-fpm-5.4.16, MariaDB-server-10.0.22
Thanks in advance for any help!
Yep, similar problems here as well...
Btw, does your shoutbox work (assuming that you are using one)?
And yep I am on a CentOS 7 server as well :-)
We don't have shoutbox.
Hi ptankov,
frankly I could not resolve the issue...
Thankfully, I had fully backed-up everything a couple of days before the patch...
So basically I re-uploaded my backed up files and the forum is up and running again smoothly.
The problem appeared to be that the "username" and "password" did not match; hence did not allow me to even enter the forums... yet; everything was correct.
Hence, I used my backup files....
The only drawback is the fact that the shoutbox does not work anymore; so currently I have disabled it until I can figure out the problem.
Bottom line is this: if you want to solve the issue quickly use your backup files. :)
Apparently, and from what I get, is that this new patch has caused more problems than solving them...
Ah... I am betting that you did not apply the patch update to your custom theme, which includes an update the to login functionality....
I have no idea why the update would remove thebdatabase connection and I can not replicate the issue on any of 4 different servers...
Not all servers use the same configuration, that is specific and should be provided by the host.
Your advice only applies to very specific server config, and is not suitable for general use. Please do not post it again.
Quote from: Sir Osis of Liver on May 16, 2017, 05:53:34 PM
Your advice only applies to very specific server config, and is not suitable for general use. Please do not post it again.
Whose advice? I don't get it.
it was posted by WesternDigi but the posts were removed.
Quote
Ah... I am betting that you did not apply the patch update to your custom theme, which includes an update the to login functionality....
I do not know if you are referring to my case, but I did apply the patch to the custom theme (also the new patch passed the test successfully in regards to the custom theme as well).
Moreover, my problem was not only the login functionality but I could not open any page of the forum at all... so I was able to solve all issues (the one of the shoutbox included) by uploading the backup files.
Apart from it, I was taken by surprise because in the past, whatever patch, or upgrade, I did apply they never caused a problem at all... on the contrary I might say.
I can't upgrade my forum. Please, can anybody tell me how to see detailed error log from php-fpm on CentOS?
this topic is getting very hard to follow. you did not open the topic unless you are talking about the same forum please open your own topic so we can help you correctly.
My problem is identical to the OP. If I create a new topic I'd have to basically just copy what OP said.
sorry that is our policy, each user should have their own topic so we can help them.