Graveyard server moves
Posted (September 24th, 2007 at 5:58 pm PST) by kitchenContinuing with our datacenter re-arranging tonight we’ll be moving 2 mysqls from one rack to another.
mimsey
figaro
We will be moving these at 1am pacific time, and the downtime should be no more than 15 minutes. We will post another update here when the moves are complete.
Update: 1:06am pacific: The moves are beginning now. We will post another update when they are completed.
Update: 1:19am pacific: The moves have been completed and everything should be fine!
Thank you for your patience!
Sincerely,
The Happy DreamHost Graveyard Shift Team.
12 Responses to “Graveyard server moves”
Upgrade to Wordpress 2.3!
Thank you vey much.
> Upgrade to Wordpress 2.3!
Hum… why would anyone ever do that?
Hello,
In my website couldt not connect to Database. (phpbb+joomla). … any solution?
Pd. Sorry for me bad english.
This is response in log-in to phpMyAdmin:
#2013 - Lost connection to MySQL server during query
¿Where is the problem?
Thanks.
Regards.
@Jimmy: It was a lie, look at the Slashdot article again.
Yes, please– update to Wordpress 2.3.
@ServDown - You’re not going to get any answers with those couple of posts. Even if the DH staff happened to be reading these comments (which they may or may not do), you haven’t given the server names or even the URL of the site you’re having trouble with, so there’s no way for anyone to troubleshoot.
Go through the Contact Support dialog on the panel - from the error message in your second post, it seems like you mySQL server may have gone down.
@brasscrest - I feel it by my two post. It will hope to have if the problem is solved. Thanks.
> @Jimmy: It was a lie, look at the Slashdot article again.
Not really a lie. I was following the mailing list before it even hit Slashdot. The Slashdot article was a little over the top though. The problem is that the developers were planning on putting in the code WITHOUT an announcement about it sending information (and the fact that you couldn’t disable it). The “idea” of the announcement part only came after the flamewar started. Even then the developers removed a bit of the more harmful code (sending all of $_SERVER) before release. Look at the original code the complainer posted with how to remove it. The author did basically tell people to shove it in the mailing list. A plugin to disable it was only written after he said he didn’t want to change it. The only real issue people have now is that it still is sending the URL of their blog, for no apparent reason (you certainly don’t need it to check for updates). On my part, I just wrote a plugin that allows it to check for updates, but sends http://please.respect.my.privacy.com as the URL instead. I even randomize the PHP version I send them. Great thing about Open Source, if you don’t like it, you can change it yourself.
I noticed that the linked articleon Slashdot has been updated with new information.
Cool, the post.
Thanks for the information.
Moving again?