Hello,

I'm setting up my initial Linode with Ubuntu 12.04.4LTS. adding Apache and MySQL ect. When I ssh the server I'm getting the usual System information then a line that indicates a System restart is required.

*** System restart required ***
Last login: Sun Feb 23 21:38:57 2014 from

This is probably because of the updates I've been making?

Can I restart my system from the Shell?

Many thanks

While you can, you SHOULDN'T.

Issue reboot jobs from the Linode Manager. It makes everything happy.

It's totally fine to reboot via the shell. That said, the "System restart required" banner is likely telling you that you upgraded your kernel package, which has no effect on your Linode unless you're using pv-grub.

- Les

Issuing a reboot from the shell is actually identical to issuing a shutdown; Lassie (the Linode watchdog) will then detect the system has shut down and will start it up again.

I do find some timing differences though between the shell and Linode Manager, in terms of the downtime.

Doing it from the shell shuts down faster, but then you have to wait for Lassie to notice and execute the restart job. It doesn't take long, but there is some latency.

Doing it from the manager takes a little longer to get the shutdown job going (and have the guest actually shut down), but the restart job is queued up immediately so happens faster.

So while I've done it both ways, if I have access to the manager, I tend to take that approach as while it may not change the overall time for the restart, it helps minimize the actual down time.

-- David

As akerl said, if it's a kernel update and you're not using pv grub you can ignore it, you should however reboot periodically to keep your linode kernel up to date (kernels are listed here https://www.linode.com/kernels/).

Other packages do sometimes create this flag, updates to openssl normally trigger it.

If you want to clear it without rebooting run

rm /var/run/reboot-required

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Many thanks everyone.