Repeated Reboots
Linode
Linode Staff
This morning, Dec 13th, 2018, around 07:26am EST, the Linode went into a spontaneous reboot. Per the previous occurrence, I enabled persistent boot logs. However, when I run journalctl -b -1, the log ends on Dec 9th. I can't seem to find any logs between Dec 9th and Dec 13th, to try and find the reason for these spontaneous reboots.
A failure to start a service is hardly a plausible reason for a reboot. Journal corruption sounds more like an effect of a reboot rather than a cause. I have checked /var/log/dmesg, and it only contains the log of the last boot, while /var/log/messages simply "cuts" the logging prior to boot with no clear symptoms:
Dec 13 07:25:01 host2 systemd: Created slice User Slice of ebook.
Dec 13 07:25:01 host2 systemd: Started Session 11101 of user ebook.
Dec 13 07:25:01 host2 systemd: Created slice User Slice of root.
Dec 13 07:25:01 host2 systemd: Started Session 11100 of user root.
Dec 13 07:25:01 host2 systemd: Removed slice User Slice of ebook.
Dec 13 07:25:04 host2 systemd: Removed slice User Slice of root.
Dec 13 07:26:07 host2 kernel: Initializing cgroup subsys cpuset
Dec 13 07:26:07 host2 kernel: Initializing cgroup subsys cpu
Dec 13 07:26:07 host2 kernel: Initializing cgroup subsys cpuacct
Dec 13 07:26:07 host2 kernel: Linux version 3.10.0-957.1.3.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Thu Nov 29 14:49:43 UTC 2018
Dec 13 07:26:07 host2 kernel: e820: BIOS-provided physical RAM map:
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007ffddfff] usable
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x000000007ffde000-0x000000007fffffff] reserved
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
Dec 13 07:26:07 host2 kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
07:26:07 is the time when reboot seemed to have happened. Any thoughts / ideas you could provide would be really helpful. Thanks!
1 Reply
Hey there,
I would say that the best way to start troubleshooting this is to figure out why there was a gap in your logs as it may provide an indication of the source of the problem.
I recommend that when you reboot, you check the status of your journald.service to see that it's starting properly.
$ systemctl status systemd-journald.service
I recommend you do the same with the socket:
$ systemctl status syslog.socket
I would then check your configuration to see if you have limits on the maximum disk space that can be used for your logs:
$ sudo journalctl -u systemd-journald
If those both seem to be in order, you can pull journalctl output with more information about any errors using the following:
[https://www.freedesktop.org/software/systemd/man/journalctl.html#-x]
Sincerely,
Tara T
Linode Support Team