After somebody tried to break into my server using one of the more recent security leaks in a Linux installation I thought it would be time to update vmgump.apache.org as well. I've done remote system updates with and without reboots at least a hundred times both at work as well as with my own servers. I never had any problems, but I always knew whom to call if anything bad should happen.
This time I didn't have a phone number and driving to the colo wasn't an option either. I had this "will this go well?" feeling when I typed "shutdown -r now" but still proceeded. Guess what, the machine hasn't come back to live yet.
I've broken Gump builds by breaking the Ant bootstrap process before, but at least I could fix it myself. This time I can only wait for somebody with proper karma to help out. I guess I'll stay away from sysadmin stuff in the future.
path: /en/Apache/Gump | #