Machine stopped responding without any indication in syslog

Latest response

My machine stopped responding, including to the console.
After a reboot, I looked at the syslog, and these are the messages just before the reboot:

May 7 12:00:01 seppuku systemd: Removed slice user-0.slice.
May 7 12:00:01 seppuku systemd: Stopping user-0.slice.
May 7 12:01:01 seppuku systemd: Created slice user-0.slice.
May 7 12:01:01 seppuku systemd: Starting user-0.slice.
May 7 12:01:01 seppuku systemd: Started Session 25183 of user root.
May 7 12:01:01 seppuku systemd: Starting Session 25183 of user root.
May 7 12:01:01 seppuku systemd: Started Session 25182 of user qa.
May 7 12:01:01 seppuku systemd: Starting Session 25182 of user qa.
May 7 12:01:02 seppuku systemd: Removed slice user-0.slice.
May 7 12:01:02 seppuku systemd: Stopping user-0.slice.
May 7 12:26:42 seppuku rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="1126" x-info="http://www.rsyslog.com"] start
May 7 12:26:08 seppuku kernel: microcode: microcode updated early to revision 0x20, date = 2016-03-16
May 7 12:26:08 seppuku kernel: Initializing cgroup subsys cpuset
May 7 12:26:08 seppuku kernel: Initializing cgroup subsys cpu
May 7 12:26:08 seppuku kernel: Initializing cgroup subsys cpuacct
May 7 12:26:08 seppuku kernel: Linux version 3.10.0-514.10.2.el7.x86_64 (mockbuild@x86-039.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Mon Feb 20 02:37:52 EST 2017
May 7 12:26:08 seppuku kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-514.10.2.el7.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet LANG=en_US.UTF-8
May 7 12:26:08 seppuku kernel: e820: BIOS-provided physical RAM map:
May 7 12:26:08 seppuku kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
May 7 12:26:08 seppuku kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
May 7 12:26:08 seppuku kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
May 7 12:26:08 seppuku kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved

Since nothing indicates a root-cause for the problem, can you suggest where I could search for more data as to why my machine had to be rebooted?

Responses

Hello Ron,

In such cases, it is recommended to configure kdump which would facilitate in understanding system state when crash happened or when system was un-responsive or locked up. Please refer the below article to understand kdump and how to configure it: https://access.redhat.com/solutions/6038

I hope this helps. All the best!