Uptime no more... I hope
First off, I'd like to extend my deepest apologies for this evening's extended downtime. It was a combination of poor planning and execution that led to the downtime, and it shouldn't happen again.
It started out with a RAM upgrade from 512MB to 1GB today. My kernel happened to be old and not support 1GB of RAM, and so I needed to upgrade. I found the proper kernel in the apt-get repositories and installed it, all smoothly. After I had installed the new kernel I typed 'telinit 0' (shutdown)instead of 'telinit 6' (restart). Normally this wouldn't be too big of a problem: it would shut down and then I would go to the Remote Reboot panel, type in my password and reboot the machine. Unfortunately I couldn't remember my password for the remote reboot panel, so I requested a new password. This, of course, was tied to my email account hosted on the machine that was, of course, not running at the moment. At that point I emailed tech-support to have the machine booted up from their end of the connection. That worked, and now everything is working as expected.
My deepest apologies,
Graham Christensen
It started out with a RAM upgrade from 512MB to 1GB today. My kernel happened to be old and not support 1GB of RAM, and so I needed to upgrade. I found the proper kernel in the apt-get repositories and installed it, all smoothly. After I had installed the new kernel I typed 'telinit 0' (shutdown)instead of 'telinit 6' (restart). Normally this wouldn't be too big of a problem: it would shut down and then I would go to the Remote Reboot panel, type in my password and reboot the machine. Unfortunately I couldn't remember my password for the remote reboot panel, so I requested a new password. This, of course, was tied to my email account hosted on the machine that was, of course, not running at the moment. At that point I emailed tech-support to have the machine booted up from their end of the connection. That worked, and now everything is working as expected.
My deepest apologies,
Graham Christensen
