Derek Zeanah
May 2, 2008, 04:50 PM
Well that just sucked.
I'm up in Atlanta messing around with the servers, and I downed the database server by mistake (I brought it down cleanly, but I identified it by the box it was in rather than by the label on it) rather than the vB box.
Then, when it came back up, I got DB errors. Everything looked fine, but I still got db errors. Ended up doing a check/repair/optimize-while-I'm-at-it because I was out of ideas, then I checked e-mail to get a look at the error description.
It was something like "there were too many connection errors, so the database server stopped you from connecting to itself. Run xxxxxxxxxxx to fix it."
Weird.
And that's why we were down. It went from "the servers are a little hot and I'm in Atlanta anyway so I'll take 10 minutes to rearrange them" to SNAFU.
Sorry.
I'm up in Atlanta messing around with the servers, and I downed the database server by mistake (I brought it down cleanly, but I identified it by the box it was in rather than by the label on it) rather than the vB box.
Then, when it came back up, I got DB errors. Everything looked fine, but I still got db errors. Ended up doing a check/repair/optimize-while-I'm-at-it because I was out of ideas, then I checked e-mail to get a look at the error description.
It was something like "there were too many connection errors, so the database server stopped you from connecting to itself. Run xxxxxxxxxxx to fix it."
Weird.
And that's why we were down. It went from "the servers are a little hot and I'm in Atlanta anyway so I'll take 10 minutes to rearrange them" to SNAFU.
Sorry.