Yeah, the Wildebeest got a bit of a strangle in the last 24 hours. I decided that since my load graphs as http://tim.gm.skudd.com/ had shown basically no activity on the three project servers that I have running, I would fix it. So, I dropped the Folding@Home client on each (as root), and fired it up. When I woke up this morning, nothing worked, the Wildebeest, Boardbox, and Shazpod were all non-responsive, and I was left looking like an idiot.
I don't think the sister unit and her husband are around today, so the 'beest is still dead-ish. I've left instructions with them on how to fix it, so it's just a matter of waiting for them to get home.
Shazpod was pretty easy to fix, since I had my KVM hooked up to it still from the initial setup. Boardbox, on the other hand, was a much different story. I don't know if it's the hardware or what, but that was the second time I saw what appeared to be a spazzed-out video card, and the system was 100% unresponsive. As such, I had to issue a hard reboot, and it's back online now.
So yeah, if you use the Wildebeest, I apologize for the downtime. Such is life of a project server.