As is the standard, the server decided to wait until a few hours after I was asleep, but a few hours before I would wake up to die. I did not have time before work to diagnose what happened, all I know is that the server was not responding to connections, even SSH from the internal network. I did a hard boot and restarted the server processes.
Last I saw before it went down it was in the 90 Gh/s range. My Estimated Rewards correlated to that. Database and/or bitcoind logging overload? Not sure why it would lock up the rest of the system unless there was a memory leak introduced somewhere in the upgrades or temp/log files were eating up a lot of hard drive space.
New hardware is always awesome but almost almost always causes it's own problems.
) comcast nodes/gates]is to take down connection services for bogus reasons or without reasons for all[maybe after class-act lawsuit something change]. 
