Why did system reboot itself?
* linode... - (56441940) Host initiated restart - Completed Mon, 11 Sep 2017 20:54:42 GMT * linode... - (56443732) Lassie initiated boot: My Ubuntu 16.04 LTS Profile - Failed Mon, 11 Sep 2017 20:54:47 GMT
The system rebooted just fine, but I don't understand why it rebooted.
I had logged into the system the day before, CPU usage is very low 2-5%, and free -m showed only 20% of swap being used, after being up for 60 days.
I looked at /var/log/syslog, and it does not indicate how/why this system rebooted.
Was the machine this VPS on restarted, is that a possible reason for no messages related to this reboot reason in syslog?
The syslog entries look similar to the ones when I manually run "sudo reboot" on my box, except there are no "Stopping" or "Stopped" service messages in this case.
syslog snippet - nothing before 16:54 at all indicating why it shut down:
Sep 11 16:09:01 linode CRON: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Sep 11 16:54:50 linode rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="3345" x-info="http://www.rsyslog.com"] start Sep 11 16:54:50 linode rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ] Sep 11 16:54:50 linode rsyslogd: rsyslogd's groupid changed to 108 Sep 11 16:54:50 linode rsyslogd: rsyslogd's userid changed to 104 Sep 11 16:54:50 linode rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ] Sep 11 16:54:50 linode rsyslogd-2007: action 'action 10' suspended, next retry is Mon Sep 11 16:55:20 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Sep 11 16:54:50 linode kernel: Linux version 4.9.36-x86_64-linode85 ([email protected]) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Thu Jul 6 15:31:23 UTC 2017 Sep 11 16:54:50 linode kernel: Command line: root=/dev/sda console=tty1 console=ttyS0 ro devtmpfs.mount=1 Sep 11 16:54:50 linode kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Sep 11 16:54:50 linode kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Sep 11 16:54:50 linode kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Sep 11 16:54:50 linode kernel: x86/fpu: xstate_offset: 576, xstate_sizes: 256 Sep 11 16:54:50 linode kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Sep 11 16:54:50 linode kernel: x86/fpu: Using 'eager' FPU context switches. Sep 11 16:54:50 linode kernel: e820: BIOS-provided physical RAM map: Sep 11 16:54:50 linode kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable ...
system rebooted successfully.
I'm surprised that nothing in syslog or auth.log corresponds to the email alert "Host initiated …"
I only see this in auth.log:
Sep 11 16:54:50 linode systemd-logind: Watching system buttons on /dev/input/event0 (Power Button)
Sep 11 16:54:50 linode systemd-logind: New seat seat0.
So between this and syslog, I should have expected log lines to indicate a host initiated restarts.
In any case, I do see that line in the manager.linode.com Host Job Queue section, so now I know what "host initiated" means, thanks!
If what you see instead is a Lassie initiated boot, that means your Linode was registered as unresponsive by our hypervisor and was forced to close. In this case, our shutdown watchdog called Lassie would boot the Linode back up. For Lassie initiated boots, you will want to look into your system's logs to see if you can find a reason for why your Linode was registered as unresponsive. You can read a bit more about how Lassie works here:
If there's anything else we can do, just let us know!