BUCKYLE;1274328; said:Seriously, C, you don't ever need to apologize to anyone here for anything. Thanks for hookin' us back up!
I do though. The needs of the site, from a technical standpoint, have surpassed my limited ability to manage them, and I have few answers in regards to what to do about that. The crash we suffered today was clearly hardware related, which is what caused this later corruption. The problem is, no one has any idea (least of all me) what piece of hardware may be causing the problem. When Puregig rebooted us, they hooked up a monitor, and it was just a blank/black screen, no feedback whatsoever.
So now I'm just waiting for another crash. Our last was on the 16th, and then another today on the 27th. The good news is reboots have brought the site back online, and now that I know that the crashes can cause these sorts of databases problems, I'll be making sure I go through and check (and where necessary repair) all tables after it happens again, which should prevent this sort of extra tomfoolery.
I'm copying our database and file directories to my local machines here right now, just in case something absolutely horrible happens, so there's little chance we could lose everything -- but not knowing when the next shoe will drop is very frustrating and stressful.
My interest has always been the community/people/discussion side of the site, and the technical demands have largely robbed me of that over the last few years. I need to come up with some sort of solution that would afford us better managed care and oversight, meaning, someone with a clue -- but I don't really know where to start. We should also probably have some hardware redundancy. A couple smaller machines perhaps and a load balancer, which might even be cheaper than another big single loaded box -- but that's neither here nor there.
Anyway, I am sorry, because I can't promise we won't crash again, and there's nothing (at present) I can do to prevent that. All I can say is that if and when it happens, I'll call for a reboot asap, and check the databases immediately thereafter.
Upvote
0