I just found out that a system restarted a few days ago and I'm trying to identify the cause or to see if this is going to be a problem that might get worse. Here is the output from the messages log file for the time that it reboot which was 10:49

Nov 1 10:40:02 ggaux1 systemd: Removed slice User Slice of root.
Nov 1 10:40:02 ggaux1 systemd: Stopping User Slice of root.
Nov 1 10:49:30 ggaux1 kernel: microcode: microcode updated early to revision 0x200004d, date = 2018-05-15
Nov 1 10:49:30 ggaux1 kernel: Initializing cgroup subsys cpuset
Nov 1 10:49:30 ggaux1 kernel: Initializing cgroup subsys cpu
Nov 1 10:49:30 ggaux1 kernel: Initializing cgroup subsys cpuacct
Nov 1 10:49:30 ggaux1 kernel: Linux version 3.10.0-862.11.6.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Tue Aug 14
21:49:04 UTC 2018
Nov 1 10:49:30 ggaux1 kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-862.11.6.el7.x86_64 root=/dev/mapper/vg_ggaux1-lv_root ro crashkernel=auto rd.lvm.lv=vg_ggaux1/lv_root rd.
lvm.lv=vg_ggaux1/lv_swap rhgb quiet LANG=en_IE.UTF-8
Nov 1 10:49:30 ggaux1 kernel: e820: BIOS-provided physical RAM map:
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000003dfff] usable
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000000003e000-0x000000000003ffff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x0000000000040000-0x000000000009ffff] usable
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000005b871fff] usable
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000005b872000-0x000000005e15ffff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000005e160000-0x000000005e287fff] ACPI data
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000005e288000-0x000000006d8f7fff] ACPI NVS
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000006d8f8000-0x000000006f317fff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000006f318000-0x000000006f7fffff] usable
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x000000006f800000-0x000000008fffffff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed44fff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 1 10:49:30 ggaux1 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov 1 10:49:30 ggaux1 kernel: NX (Execute Disable) protection: active
Nov 1 10:49:30 ggaux1 kernel: extended physical RAM map:





The logs go on for quite a bit after this so if you need more info I can provide it.

Thanks for any assistance.

I can't see anything in your above post that stands out, it all looks quite normal to me. But of course random restarts ain't normal though.

Have a look though your kernel log for anything that looks like an error message, and better still, attach the results of the following command to your next post;

If there are no errors logged there, it could be a hardware and/or a power issue of some kind.

Hi js,

thanks for your response. Attached is the dmesg output that you requested

Attached Files

kernellog.txt (150.1 KB, 35 views)

Looks like something is causing a panic and making your computer restart after a set amount of time. The restarts are only a side effect of what's really going on. Can you echo /proc/sys/kernel/panic and /proc/sys/kernel/panic_on_* and tell us what they say?

Hi Rik,

I take it you meant to cat those files rather than echo them?

All the files that you mentioned are empty:

-rw-r--r--. 1 root root 0 Nov 9 11:19 numa_balancing
-rw-r--r--. 1 root root 0 Nov 9 11:19 numa_balancing_scan_delay_ms
-rw-r--r--. 1 root root 0 Nov 9 11:19 numa_balancing_scan_period_max_ms
-rw-r--r--. 1 root root 0 Nov 9 11:19 numa_balancing_scan_period_min_ms
-rw-r--r--. 1 root root 0 Nov 9 11:19 numa_balancing_scan_size_mb
-rw-r--r--. 1 root root 0 Nov 9 11:19 numa_balancing_settle_count
-r--r--r--. 1 root root 0 Nov 9 11:19 osrelease
-r--r--r--. 1 root root 0 Nov 9 11:19 ostype
-rw-r--r--. 1 root root 0 Nov 9 11:19 overflowgid
-rw-r--r--. 1 root root 0 Nov 9 11:19 overflowuid
-rw-r--r--. 1 root root 0 Nov 9 11:19 panic
-rw-r--r--. 1 root root 0 Nov 9 11:19 panic_on_io_nmi
-rw-r--r--. 1 root root 0 Nov 9 11:19 panic_on_oops
-rw-r--r--. 1 root root 0 Nov 9 11:19 panic_on_stackoverflow
-rw-r--r--. 1 root root 0 Nov 9 11:19 panic_on_unrecovered_nmi
-rw-r--r--. 1 root root 0 Nov 9 11:19 panic_on_warn
-rw-r--r--. 1 root root 0 Nov 9 11:19 perf_cpu_time_max_percent
-rw-r--r--. 1 root root 0 Nov 9 11:19 perf_event_max_sample_rate
-rw-r--r--. 1 root root 0 Nov 9 11:19 perf_event_mlock_kb
-rw-r--r--. 1 root root 0 Nov 9 11:19 perf_event_paranoid
-rw-r--r--. 1 root root 0 Nov 1 10:49 pid_max
-rw-r--r--. 1 root root 0 Nov 9 11:19 poweroff_cmd
-rw-r--r--. 1 root root 0 Nov 9 11:19 print-fatal-signals
-rw-r--r--. 1 root root 0 Nov 9 11:19 printk
-rw-r--r--. 1 root root 0 Nov 9 11:19 printk_delay
-rw-r--r--. 1 root root 0 Nov 9 11:19 printk_ratelimit
-rw-r--r--. 1 root root 0 Nov 9 11:19 printk_ratelimit_burst
dr-xr-xr-x. 1 root root 0 Nov 1 10:50 pty



[root@ggaux1 kernel]# cat panic
0
[root@ggaux1 kernel]#

How long has the "random restarts" been happening for?
Did you do any updates when this started happening? If so, do you know what they where?
Have you installed anything from outside of the CentOS online software repositories?
Have you checked your machine's hardware?
Have you checked to make sure your machine has a good power source/supply?

Yes, I meant to cat them. My bad.

Moved: This thread is more suitable in <CentOS> and has been moved accordingly to help your thread/question get the exposure it deserves.