Hi hoodleehoo,
Sounds like a coincedence – the error means that the database server could not be reached. UD doesn’t have powers to do that, so I’d suppose that it went away for some other reason (perhaps was being restarted by its admin), and was back during the time-frame in which you were disabling the plugin.
David
I wouldn’t think so, as one of the fixes suggested online was to disable plug-ins and find the one that is causing the problem.
When wp did the repair of the database it said there was an error that it couldn’t repair and the error was something like “2 clients are using or haven’t closed the table properly”. I found someone asking WP about this error message and they said to deactivate the plugins. I deactivated updraft and it fixed the problem.
I’m assuming updraft is the “client” that was using or hadn’t closed the table properly?
Ok, I looked into it and it looks like the host was doing some work on the database and that’s causing the problem. I think you are right, it was just a coincidence. Thanks for getting back to me! 🙂
Thanks – if you find UpdraftPlus useful, then please give us a good review: http://wordpress.org/support/view/plugin-reviews/updraftplus?rate=5#postform
Best wishes,
David
HELP!
i updated the plugin and also got the message:
“Error establishing a database connection”
This either means that the username and password information in your wp-config.php file is incorrect or we can’t contact the database server at sql-2.interip.nl. This could mean your host’s database server is down.
What do I have to do to get the website back online!!!!
Hi,
Sorry to hear about that! No WordPress plugin has the powers (even if they wanted to) to make the database connection go away, so this is just an unfortunate coincidence… you’ll want to talk to whoever is responsible for the database server to see what they can do to get it back up…
David
The only thing i did was updating the updraftplus plugin.
Now the whole site is offline.
I renamend the plugins folder, and after 10 minutes i was able to see the website again.
(the only plugin i am using right now is the updraftplus)
I got almost a heart attack.
The fact that there was a 10 minute delay shows that you’re just drawing inferences from co-incident events. If one caused the other, then it would be instant. WordPress plugins are installed at the rate of hundreds of thousands a day. Peoples’ database servers crash at the rate of thousands a day. Sometimes those events will have the same approximate timing. If one was the responsible cause of the other, then the timing would be *exact*. If it were possible to make a database server restart itself by renaming a plugin, then that would basically be magic. (It’s possible that activating a plugin could be the *immediate* cause in the sense that the database server may be totally overloaded and the commands that result from the activation may be the straw that breaks the camel’s back – but it can’t be the *responsible* cause; that would be that the database server is overloaded. As I said, there’s no possible mechanism for a plugin to do this even if it wants to. The true cause has to be elsewhere).
Best wishes,
David
