Bitch, whine, moan.
For the most part, I'd been happy with them, but my freakin' server has been down for over three hours now.
No response to support requests. A notice on the support site posted two hours ago, saying they know they're fucked up and will post with updates.
Nothing else.
GRRRRRRRRRRRRR
I wanted to come back with an updated. I am a bitch so I asked for . . . details . . . more than just the "we had a problem and we fixed it" that I received in response to my request. And I got a pretty detailed answer. It doesn't chage the fact that we were down for 3 hours, but shit does happen, especially when you share a server, like I currently am.
Quote:Response:
--------------
- A customer ran untested code on the server which looped endlessly on
itself, exhausting resources and writing huge numbers of files to the
/tmp directory. Ultimately the server became unresponsive.
- Server was rebooted.
- Because files were being written to the /tmp directory at the time
the server was hard rebooted, the server detected file system corruption
during the reboot.
- At this point a decision had to be made: chance it and hope that the
filesystem was ok, or initiate a full filesystem check. Given that it's
a holiday Saturday and that a filesystem error is a bad thing at the
best of times, a full check was initiated. This entailed running the
Linux equivalent of chkdisk on more than 300GB of hard drives.
- The filesystem check completed, the errors (which were all files in
/tmp) were corrected, and the server was brought back up.
Unfortunately this kind of thing will happen occasionally in shared
environments when people decide that a production web server is the ideal
test platform for their latest efforts. Everything possible was done to
minimize the downtime caused whilst keeping data integrity as the
paramount priority.
The customer concerned is now an ex-customer.
(Beth's true confession - a gazillion years ago, in undergrad, I took my first and only computer science class. I'm old, so at the time this meant there was a monster size computer in its own cooled room and a bunch of terminals outside hooked to it. I wrote and ran an endless loop. I was just a baby at the time - 16 - and wanted to just freakin' die when the lab rat came out and yelled across the crowded room something charming like "who's the moron running an endless loop"?)