fremont40 encountered a Xen bug and required a reboot. We took this opportunity to update to our latest Xen stack and Linodes are booting up now.

-Tom

Can you post any details on the Xen bug? I've checked the logs on our DomU, but didn't find any suspicious messages. Did the upgrade to a newer Xen version had anything to do with the bug you mentioned?

It happened to dom0, of course you wouldn't see anything in your domU's logs. As well, they took advantage of a crash and instead of just booting back up the dom0 they updated it, so that hopefully, the crash doesn't occur from the same bug.

_________________
If it ain't broke, you didn't tweak it enough. If it is broke, use more duct tape.
http://independentchaos.com

Is there any way that the customers with an instance on a rebooted server can get an email notification when a server is rebooted? We see anomalies in some logs and some unexpected emails on reboot, and it would be nice to know that the server was rebooted without digging through all the logs or checking this forum.

Thanks.

- Jerry

While that would be a nice config option on the control panel, I'll point out that you could easily put something into the rc.local (or equivalent) of your linode to accomplish the same.

Except that doing that only lets you know that your Linode rebooted, not that the host was rebooted. Presumably a non-host-related reboot will require more investigation and troubleshooting to understand what happened. I also think it would be nice to have an option for administrative email notifications - perhaps an option in Linode Manager to get email about jobs for a Linode, since the reboot is performed through insertion of a job.

To the OP, although emails aren't currently generated, this forum seems used consistently. You could monitor an RSS feed for this forum (use the additional RSS options link at the bottom of the forum page to generate an appropriate URL) and watch for your host, then send yourself some mail. That should also catch any notices related to your host that might not actually be a full reboot.

Alternatively, with the new Linode API just released (http://www.linode.com/api/autodoc.cfm), you could monitor the jobs for your Linode, since reboot jobs are submitted after a host reboot. This approach could also cover any locally initiated reboots, flagging any case where the Linode was rebooted explicitly through a manager job. Or if you just want system initiated reboot jobs such as after a host reboot, I believe they have a unique job date in 1974 (I think I saw a reference elsewhere that it was caker's birthday) that while not guaranteed, should make them easily identifiable.

In the API case, if you didn't want to bother setting up a polling task, you could mix this with glg's idea - just have your Linode check its own jobs once at reboot, to see if it can find a Linode Manager job to explain the restart. Not sure you could use the RSS case for this, since the posting may not yet have been made to the forum by the time the Linode is rebooting.

-- David

I actually just created a service for this that I'm testing out right now. If you are willing to suffer through the beta head over to http://spafw.net . The whole point of that site is to notify you on host reboots via twitter or email.
</shameless self plug>