Quote:
Originally Posted by bevischief
Was it a hardware or software problem? You can PM the answer if would you like just curious. Not suing like some would like to try do.
|
ID 10 T error by me.
kind of a perfect storm of screw ups. I let the log files go without pruning too long and they filled up a partition that caused the server to crash. No big deal really because it should then reboot and clean things up. Down for just a few minutes... BUT a few months back I was going to upgrade us to VB5 so I set up a clone of the db and went through the steps to make a BETA site for testing. It turned out that VB5 was a complete disaster and not at all ready for prime time. So, I decided to wait for VB5.1 and hope that wouldn't be such a complete failure. Well, I left the VB5 db up so it could easily be upgraded when it came time to test VB5.1. It turns out that the VB5 database tables are so slipshod that when the server rebooted it couldn't even start the MYSQL(our database server) service. I had to go in and manually remove that entire db and do a bunch of nonsense then reboot the machine yet again. THEN the database service had a bunch of "catching up" and maintenance to do before the server settled down.
So that is why it was down for hours instead of minutes.
(Oh and the alerts starting coming in around 8am but I didn't actually get my ass up until 8:30 to start working on it)