Workstation Uninstructed Reboot

General support questions
CaveDann
Posts: 23
Joined: 2018/12/14 15:05:27
Location: UK

Workstation Uninstructed Reboot

Post by CaveDann » 2019/09/25 10:14:54

Hello,

I'll provide as much info as I can on this. I'm not particularly well versed in dealing with error logs though so forgive me if I'm not performing otherwise obvious steps.

Over the past 6 months, one of my PC's has been randomly rebooting itself without being instructed to do so. This has happened on all of CentOS 6.6, 6.7, 6.9 and now 7.6 too. Posting to CentOS 7 General as 7 is the desired OS for this PC.

Throughout using CentOS 6, no error logs were produced as part of this process. Simply, the logs would show that the machine was operating normally, then log that the kernal was being initialised as the system powered back up.

Now in CentOS 7.6, /var/log/messages is recording some additional information.

Code: Select all

Sep 24 10:54:44 proto journal: unable to create file '/run/user/3169/dconf/user': Permission denied.  dconf will not work properly
Sep 24 11:06:13 proto journal: clutter_actor_contains: assertion 'CLUTTER_IS_ACTOR (descendant)' failed
Sep 24 11:06:13 proto journal: clutter_actor_contains: assertion 'CLUTTER_IS_ACTOR (descendant)' failed
Sep 24 11:06:56 proto org.gnome.Shell.desktop: Window manager warning: last_user_time (613871502) is greater than comparison timestamp (613870574).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Sep 24 11:06:56 proto org.gnome.Shell.desktop: Window manager warning: 0x2e00010 (Walking To) appears to be one of the offending windows with a timestamp of 613871502.  Working around...
Sep 24 11:07:02 proto journal: pushModal: invocation of begin_modal failed
Sep 24 11:09:15 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/S
essionManager/Client10' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Clien
t '/org/gnome/SessionManager/Client10' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client8' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client7' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client6' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client5' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client4' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client3' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client1' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client29' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client28' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client25' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client24' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client22' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client20' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client34' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client8' failed to reply before timeout
Sep 24 11:09:16 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client19' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client30' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client13' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client12' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client11' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session: gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client9' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client7' failed to reply before timeout
Sep 24 11:09:17 proto journal: Failed to send session response Timeout was reached
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client6' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client5' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client4' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client3' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client1' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client29' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client28' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client25' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client24' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client22' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client20' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client34' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before timeout
Sep 24 11:09:17 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client19' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client30' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client13' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client12' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client11' failed to reply before timeout
Sep 24 11:09:18 proto gnome-session-binary[11552]: WARNING: Client '/org/gnome/SessionManager/Client9' failed to reply before timeout
Sep 24 11:09:18 proto gnome-keyring-daemon[10802]: dbus failure responding to ending session: Timeout was reached
Sep 24 11:09:36 proto journal: Failed to call Shutdown on session manager: Timeout was reached
Sep 24 11:16:16 proto kernel: accounts-daemon invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
Sep 24 11:16:16 proto kernel: accounts-daemon cpuset=/ mems_allowed=0
Sep 24 11:16:16 proto kernel: CPU: 0 PID: 3631 Comm: accounts-daemon Kdump: loaded Not tainted 3.10.0-957.el7.x86_64 #1
Sep 24 11:16:16 proto kernel: Hardware name: Dell Inc. Precision 3630 Tower/0NNNCT, BIOS 1.1.6 12/14/2018
Sep 24 11:16:17 proto kernel: Call Trace:
Sep 24 11:16:17 proto kernel: [<ffffffffa6b61dc1>] dump_stack+0x19/0x1b
Sep 24 11:16:17 proto kernel: [<ffffffffa6b5c7ea>] dump_header+0x90/0x229
Sep 24 11:16:17 proto kernel: [<ffffffffa670095b>] ? cred_has_capability+0x6b/0x120
Sep 24 11:16:17 proto kernel: [<ffffffffa65ba274>] oom_kill_process+0x254/0x3d0
Sep 24 11:16:17 proto kernel: [<ffffffffa6700a2c>] ? selinux_capable+0x1c/0x40
Sep 24 11:16:17 proto kernel: [<ffffffffa65baab6>] out_of_memory+0x4b6/0x4f0
Sep 24 11:16:17 proto kernel: [<ffffffffa6b5d2ee>] __alloc_pages_slowpath+0x5d6/0x724
Sep 24 11:16:17 proto kernel: [<ffffffffa65c0e95>] __alloc_pages_nodemask+0x405/0x420
Sep 24 11:16:17 proto kernel: [<ffffffffa6611105>] alloc_pages_vma+0xb5/0x200
Sep 24 11:16:17 proto kernel: [<ffffffffa65e96c7>] handle_pte_fault+0x887/0xd10
Sep 24 11:16:17 proto kernel: [<ffffffffa6434919>] ? sched_clock+0x9/0x10
Sep 24 11:16:17 proto kernel: [<ffffffffa64d9ed5>] ? sched_clock_cpu+0x85/0xc0
Sep 24 11:16:17 proto kernel: [<ffffffffa642a621>] ? __switch_to+0x151/0x580
Sep 24 11:16:17 proto kernel: [<ffffffffa65ebc6d>] handle_mm_fault+0x39d/0x9b0
Sep 24 11:16:17 proto kernel: [<ffffffffa6b6f5e3>] __do_page_fault+0x203/0x500
Sep 24 11:16:17 proto kernel: [<ffffffffa6500f72>] ? ktime_get_ts64+0x52/0xf0
Sep 24 11:16:17 proto kernel: [<ffffffffa6b6f915>] do_page_fault+0x35/0x90
Sep 24 11:16:17 proto kernel: [<ffffffffa6b65ce0>] ? bit_wait+0x50/0x50
Sep 24 11:16:17 proto kernel: [<ffffffffa6b6b758>] page_fault+0x28/0x30
Sep 24 11:16:17 proto kernel: [<ffffffffa6784079>] ? copy_user_enhanced_fast_string+0x9/0x20
Sep 24 11:16:17 proto kernel: [<ffffffffa65b62ac>] ? file_read_actor+0x6c/0xa0
Sep 24 11:16:17 proto kernel: [<ffffffffa65b800d>] generic_file_aio_read+0x4bd/0x790
Sep 24 11:16:17 proto kernel: [<ffffffffc0867d93>] ext4_file_read+0x43/0x130 [ext4]
Sep 24 11:16:17 proto kernel: [<ffffffffa66404d3>] do_sync_read+0x93/0xe0
Sep 24 11:16:17 proto kernel: [<ffffffffa6640f0f>] vfs_read+0x9f/0x170
Sep 24 11:16:17 proto kernel: [<ffffffffa6641dcf>] SyS_read+0x7f/0xf0
Sep 24 11:16:17 proto kernel: [<ffffffffa6b74ddb>] system_call_fastpath+0x22/0x27
Sep 24 11:16:17 proto kernel: Mem-Info:
Sep 24 11:16:17 proto kernel: active_anon:1557626 inactive_anon:283089 isolated_anon:0#012 active_file:564 inactive_file:2060 isolated_file:0#012 unevictable:0 dirty:41 writeback:12 unstable:0#012 slab_reclaimable:14708 slab_unreclaimable:19986#012 mapped:1858 shmem:29139 pagetables:24711 bounce:0#012 free:32493 free_pcp:412 free_cma:0
Sep 24 11:16:17 proto kernel: Node 0 DMA free:15896kB min:136kB low:168kB high:204kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15896kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Sep 24 11:16:17 proto kernel: lowmem_reserve[]: 0 1747 7679 7679
Sep 24 11:16:17 proto kernel: Node 0 DMA32 free:46136kB min:15348kB low:19184kB high:23020kB active_anon:1245796kB inactive_anon:419820kB active_file:152kB inactive_file:340kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:2020196kB managed:1789604kB mlocked:0kB dirty:0kB writeback:4kB mapped:3508kB shmem:17680kB slab_reclaimable:13740kB slab_unreclaimable:17808kB kernel_stack:3168kB pagetables:22400kB unstable:0kB bounce:0kB free_pcp:1080kB local_pcp:140kB free_cma:0kB writeback_tmp:0kB pages_scanned:924 all_unreclaimable? yes
Sep 24 11:16:18 proto kernel: lowmem_reserve[]: 0 0 5932 5932
Sep 24 11:16:18 proto kernel: Node 0 Normal free:67940kB min:52096kB low:65120kB high:78144kB active_anon:4984708kB inactive_anon:712536kB active_file:2104kB inactive_file:7900kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:6225920kB managed:6077552kB mlocked:0kB dirty:164kB writeback:44kB mapped:3924kB shmem:98876kB slab_reclaimable:45092kB slab_unreclaimable:62136kB kernel_stack:11728kB pagetables:76444kB unstable:0kB bounce:0kB free_pcp:568kB local_pcp:16kB free_cma:0kB writeback_tmp:0kB pages_scanned:4411 all_unreclaimable? yes
Sep 24 11:16:18 proto kernel: lowmem_reserve[]: 0 0 0 0
Sep 24 11:16:18 proto kernel: Node 0 DMA: 2*4kB (U) 2*8kB (U) 2*16kB (U) 1*32kB (U) 3*64kB (U) 2*128kB (U) 0*256kB 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15896kB
Sep 24 11:16:18 proto kernel: Node 0 DMA32: 1552*4kB (UEM) 671*8kB (UEM) 434*16kB (UEM) 259*32kB (UEM) 114*64kB (UE) 56*128kB (UE) 19*256kB (UEM) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 46136kB
Sep 24 11:16:18 proto kernel: Node 0 Normal: 3826*4kB (UEM) 1759*8kB (UEM) 1119*16kB (UEM) 454*32kB (UEM) 80*64kB (UEM) 3*128kB (EM) 1*256kB (M) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 67568kB
Sep 24 11:16:18 proto kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Sep 24 11:16:18 proto kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Sep 24 11:16:18 proto kernel: 38632 total pagecache pages
Sep 24 11:16:18 proto kernel: 6743 pages in swap cache
Sep 24 11:16:18 proto kernel: Swap cache stats: add 2792867, delete 2786085, find 1183020/1250091
Sep 24 11:16:19 proto kernel: Free swap  = 8kB
Sep 24 11:16:19 proto kernel: Total swap = 8257532kB
Sep 24 11:16:19 proto kernel: 2065527 pages RAM
Sep 24 11:16:19 proto kernel: 0 pages HighMem/MovableOnly
Sep 24 11:16:19 proto kernel: 94764 pages reserved
Sep 24 11:16:19 proto kernel: [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
Sep 24 11:16:19 proto kernel: [ 2516]     0  2516    20377      404      46      135             0 systemd-journal
Sep 24 11:16:19 proto kernel: [ 2547]     0  2547    50272        0      33      410             0 lvmetad
Sep 24 11:16:19 proto kernel: [ 2571]     0  2571    12151       44      24      703         -1000 systemd-udevd
Sep 24 11:16:19 proto kernel: [ 3121]     0  3121    12005       20      27       77             0 rpc.idmapd
Sep 24 11:16:19 proto kernel: [ 3122]     0  3122    13880       24      27       88         -1000 auditd
Sep 24 11:16:19 proto kernel: [ 3124]     0  3124    21138       25      12       46             0 audispd
Sep 24 11:16:19 proto kernel: [ 3125]     0  3125    13908       23      31       72             0 sedispatch
Sep 24 11:16:19 proto kernel: [ 3149]     0  3149    57018        2      66      447             0 abrtd
Sep 24 11:16:19 proto kernel: [ 3150]     0  3150    56431       10      64      359             0 abrt-watch-log
Sep 24 11:16:19 proto kernel: [ 3151]     0  3151    56431       13      62      360             0 abrt-watch-log
Sep 24 11:16:19 proto kernel: [ 3152]     0  3152     4223        1      13       69             0 alsactl
Sep 24 11:16:20 proto kernel: [ 3155]     0  3155     5383       25      14       37             0 irqbalance
Sep 24 11:16:20 proto kernel: [ 3156]     0  3156     6127        1      17      176             0 smartd
Sep 24 11:16:20 proto kernel: [ 3157]    32  3157    17316       37      37      107             0 rpcbind
Sep 24 11:16:20 proto kernel: [ 3158]   998  3158     2144        8      10       30             0 lsmd
Sep 24 11:16:20 proto kernel: [ 3173]   999  3173   161178      630      72     2242             0 polkitd
Sep 24 11:16:20 proto kernel: [ 3174]     0  3174    22625        0      45      221             0 rngd
Sep 24 11:16:20 proto kernel: [ 3179]     0  3179     1881        8       9       19             0 gpm
Sep 24 11:16:20 proto kernel: [ 3206]     0  3206     1818       36      10       44             0 mdadm
Sep 24 11:16:20 proto kernel: [ 3207]    81  3207    19640      459      37      164          -900 dbus-daemon
Sep 24 11:16:20 proto kernel: [ 3214]   992  3214    29962       24      31       87             0 chronyd
Sep 24 11:16:20 proto kernel: [ 3221]     0  3221    64353       12      78      261             0 sssd
Sep 24 11:16:20 proto kernel: [ 3222]   172  3222    49698        7      34       87             0 rtkit-daemon
Sep 24 11:16:20 proto kernel: [ 3224]     0  3224   113450      284      87      801             0 udisksd
Sep 24 11:16:21 proto kernel: [ 3226]    70  3226    18109       22      35       96             0 avahi-daemon
Sep 24 11:16:21 proto kernel: [ 3229]    70  3229    18077        1      33       98             0 avahi-daemon
Sep 24 11:16:21 proto kernel: [ 3237]     0  3237    89575      219      96     5317             0 firewalld
Sep 24 11:16:21 proto kernel: [ 3241]     0  3241    28891       88      12       24             0 ksmtuned
Sep 24 11:16:21 proto kernel: [ 3627]     0  3627    78322      300     103      441             0 sssd_be
Sep 24 11:16:21 proto kernel: [ 3628]     0  3628    70558      167      91      183             0 sssd_nss
Sep 24 11:16:21 proto kernel: [ 3629]     0  3629    61246       23      75      239             0 sssd_pam
Sep 24 11:16:21 proto kernel: [ 3630]     0  3630    59099       24      70      209             0 sssd_autofs
Sep 24 11:16:21 proto kernel: [ 3631]     0  3631   101688      146      54      646             0 accounts-daemon
Sep 24 11:16:21 proto kernel: [ 3632]     0  3632     9181       59      22       39             0 systemd-logind
Sep 24 11:16:21 proto kernel: [ 3721]     0  3721    26866       43      53      457             0 dhclient
Sep 24 11:16:21 proto kernel: [ 3785]     0  3785   143483      117      99     2709             0 tuned
Sep 24 11:16:22 proto kernel: [ 3786]     0  3786    28216       21      57      236         -1000 sshd
Sep 24 11:16:22 proto kernel: [ 3790]     0  3790     6791        1      18       63             0 xinetd
Sep 24 11:16:22 proto kernel: [ 3793]     0  3793    49492        0      52      288             0 cupsd
Sep 24 11:16:22 proto kernel: [ 3794]     0  3794    65910     1106      67      187             0 rsyslogd
Sep 24 11:16:22 proto kernel: [ 3797]    29  3797    11129        1      26      210             0 rpc.statd
Sep 24 11:16:22 proto kernel: [ 3807]     0  3807   238720       80     157     2203             0 libvirtd
Sep 24 11:16:22 proto kernel: [ 3810]     0  3810     6476        0      18       52             0 atd
Sep 24 11:16:22 proto kernel: [ 3811]     0  3811    31570       28      20      130             0 crond
Sep 24 11:16:22 proto kernel: [ 3812]     0  3812   122930        0      57      307             0 gdm
Sep 24 11:16:22 proto kernel: [ 3826]     0  3826    12489        1      31      464             0 rpc.mountd
Sep 24 11:16:22 proto kernel: [ 3971]     0  3971   166620      133      68      470             0 automount
Sep 24 11:16:22 proto kernel: [ 4071]     0  4071    50327       12      39      124             0 gssproxy
Sep 24 11:16:22 proto kernel: [ 4308]     0  4308    22934       18      45      243             0 master
Sep 24 11:16:22 proto kernel: [ 4317]    99  4317    15557        0      31      111             0 dnsmasq
Sep 24 11:16:22 proto kernel: [ 4318]     0  4318    15550        1      31       97             0 dnsmasq
Sep 24 11:16:22 proto kernel: [ 4321]    89  4321    25537       22      47      245             0 qmgr
Sep 24 11:16:22 proto kernel: [ 4457]     0  4457   107557      139      61      197             0 upowerd
Sep 24 11:16:22 proto kernel: [ 4633]     0  4633    99608       91      50      133             0 boltd
Sep 24 11:16:22 proto kernel: [ 4638]     0  4638   103848      789      59      793             0 packagekitd
Sep 24 11:16:22 proto kernel: [ 4639]     0  4639    19666       14      44      184             0 wpa_supplicant
Sep 24 11:16:22 proto kernel: [ 4709]   997  4709   107455      192      60      269             0 colord
Sep 24 11:16:22 proto kernel: [ 5637]  3169  5637   904594     1590     155      854             0 pulseaudio
Sep 24 11:16:22 proto kernel: [ 5650]  3169  5650    34310        0      67      243             0 gconf-helper
Sep 24 11:16:22 proto kernel: [ 6254]     0  6254   146519      299     104      254             0 fwupd
Sep 24 11:16:23 proto kernel: [ 9258]  3169  9258    51631       12      31      306             0 oosplash
Sep 24 11:16:23 proto kernel: [ 9277]  3169  9277   486105      507     473    39278             0 soffice.bin
Sep 24 11:16:23 proto kernel: [ 9280]  3169  9280    51631        3      31      306             0 oosplash
Sep 24 11:16:23 proto kernel: [ 9295]  3169  9295   144769       14     206     5891             0 soffice.bin
Sep 24 11:16:23 proto kernel: [16146]     0 16146   246795     4127     234     4805             0 X
Sep 24 11:16:23 proto kernel: [10781]     0 10781   140583        0      87      435             0 gdm-session-wor
Sep 24 11:16:23 proto kernel: [10802]  3169 10802    71871      114      39      139             0 gnome-keyring-d
Sep 24 11:16:23 proto kernel: [10814]    42 10814   113049       11      40      255             0 ibus-daemon
Sep 24 11:16:23 proto kernel: [10819]    42 10819    93966        0      38      681             0 ibus-dconf
Sep 24 11:16:23 proto kernel: [10821]    42 10821   116205      179     113     1060             0 ibus-x11
Sep 24 11:16:23 proto kernel: [10830]  3169 10830    34099        2      20      251             0 tcsh
Sep 24 11:16:23 proto kernel: [10839]  3169 10839    17333        1      32      135             0 dbus-launch
Sep 24 11:16:23 proto kernel: [10840]  3169 10840    22043      341      34      163             0 dbus-daemon
Sep 24 11:16:23 proto kernel: [10924]  3169 10924   134024        0      51      232             0 gvfsd
Sep 24 11:16:23 proto kernel: [10929]  3169 10929   104452        0      40      750             0 gvfsd-fuse
Sep 24 11:16:24 proto kernel: [11015]  3169 11015    18105       12      37      183             0 ssh-agent
Sep 24 11:16:24 proto kernel: [11552]  3169 11552   166441      416     113     1185             0 gnome-session-b
Sep 24 11:16:24 proto kernel: [11574]  3169 11574    86699       74      37      107             0 at-spi-bus-laun
Sep 24 11:16:24 proto kernel: [11579]  3169 11579    21727       50      36      114             0 dbus-daemon
Sep 24 11:16:24 proto kernel: [11582]  3169 11582    58280      127      50      111             0 at-spi2-registr
Sep 24 11:16:24 proto kernel: [11612]  3169 11612  1097069    28600     508    42708             0 gnome-shell
Sep 24 11:16:24 proto kernel: [11652]  3169 11652    89942       28      40      492             0 ibus-daemon
Sep 24 11:16:24 proto kernel: [11657]  3169 11657    68085        0      34      188             0 ibus-dconf
Sep 24 11:16:24 proto kernel: [11659]  3169 11659    90321      183     111     1071             0 ibus-x11
Sep 24 11:16:24 proto kernel: [11661]  3169 11661    68073        0      33      188             0 ibus-portal
Sep 24 11:16:24 proto kernel: [11664]  3169 11664    65266        0      29      140             0 xdg-permission-
Sep 24 11:16:24 proto kernel: [11666]  3169 11666 25458802        0     308     3053             0 gnome-shell-cal
Sep 24 11:16:24 proto kernel: [11686]  3169 11686   121301       57      70      823             0 mission-control
Sep 24 11:16:24 proto kernel: [11688]  3169 11688    81682     1165      59      940             0 gvfs-udisks2-vo
Sep 24 11:16:24 proto kernel: [11695]  3169 11695    93719        0      48      285             0 gvfs-afc-volume
Sep 24 11:16:24 proto kernel: [11701]  3169 11701 25364718        0     170     2101             0 goa-daemon
Sep 24 11:16:24 proto kernel: [11708]  3169 11708 25599740        0     333     2881             0 evolution-sourc
Sep 24 11:16:24 proto kernel: [11716]  3169 11716    72544      127      44      602             0 gvfs-mtp-volume
Sep 24 11:16:24 proto kernel: [11721]  3169 11721    74246       34      45      201             0 gvfs-gphoto2-vo
Sep 24 11:16:24 proto kernel: [11726]  3169 11726    67004        0      34      191             0 gvfs-goa-volume
Sep 24 11:16:24 proto kernel: [11740]  3169 11740   106029       69      99      449             0 goa-identity-se
Sep 24 11:16:24 proto kernel: [11754]  3169 11754   134560      351     128     2721             0 gsd-power
Sep 24 11:16:24 proto kernel: [11756]  3169 11756   108900      127      76      306             0 gsd-print-notif
Sep 24 11:16:24 proto kernel: [11757]  3169 11757   104504       98      39       80             0 gsd-rfkill
Sep 24 11:16:24 proto kernel: [11758]  3169 11758    67661      182      35      596             0 gsd-screensaver
Sep 24 11:16:24 proto kernel: [11759]  3169 11759   113773      123      53      668             0 gsd-sharing
Sep 24 11:16:24 proto kernel: [11760]  3169 11760    92141       97      47      151             0 gsd-smartcard
Sep 24 11:16:24 proto kernel: [11761]  3169 11761   127921      351     115     1123             0 gsd-xsettings
Sep 24 11:16:24 proto kernel: [11764]  3169 11764    87837      104      72      195             0 gsd-sound
Sep 24 11:16:24 proto kernel: [11765]  3169 11765   111341      350     116     2169             0 gsd-wacom
Sep 24 11:16:24 proto kernel: [11766]  3169 11766    88290      112      40      606             0 gsd-account
Sep 24 11:16:24 proto kernel: [11768]  3169 11768    68209       93      35       77             0 gsd-a11y-settin
Sep 24 11:16:24 proto kernel: [11769]  3169 11769    90173      256     110      976             0 gsd-clipboard
Sep 24 11:16:24 proto kernel: [11770]  3169 11770   257102     1326     142     1524             0 gsd-color
Sep 24 11:16:24 proto kernel: [11771]  3169 11771   109493       90     106      449             0 gsd-datetime
Sep 24 11:16:24 proto kernel: [11772]  3169 11772    90014      213      44      605             0 gsd-housekeepin
Sep 24 11:16:24 proto kernel: [11773]  3169 11773   127610      258     117      970             0 gsd-keyboard
Sep 24 11:16:24 proto kernel: [11774]  3169 11774   291540      411     142     1457             0 gsd-media-keys
Sep 24 11:16:24 proto kernel: [11775]  3169 11775    68210       86      37      594             0 gsd-mouse
Sep 24 11:16:24 proto kernel: [11818]  3169 11818   126255       74     107      456             0 gsd-printer
Sep 24 11:16:24 proto kernel: [11873]  3169 11873   450660     1417     187     1559             0 nautilus-deskto
Sep 24 11:16:24 proto kernel: [11877]  3169 11877   116229      108      48      742             0 gvfsd-trash
Sep 24 11:16:24 proto kernel: [11884]  3169 11884   330443      314     177     3368             0 tracker-extract
Sep 24 11:16:25 proto kernel: [11886]  3169 11886    68270      176      33      132             0 gsd-disk-utilit
Sep 24 11:16:25 proto kernel: [11887]  3169 11887   152668        0      86      869             0 tracker-miner-a
Sep 24 11:16:25 proto kernel: [11888]  3169 11888   173986      753      95     1255             0 tracker-miner-f
Sep 24 11:16:25 proto kernel: [11894]  3169 11894   114565        0      84      725             0 tracker-miner-u
Sep 24 11:16:25 proto kernel: [11897]  3169 11897    88547      167     107      545             0 seapplet
Sep 24 11:16:25 proto kernel: [11898]  3169 11898   109179      177     140     1299             0 abrt-applet
Sep 24 11:16:25 proto kernel: [11900]  3169 11900 25482838      241     328     3581             0 evolution-alarm
Sep 24 11:16:25 proto kernel: [11901]  3169 11901   336950     2221     257    20793             0 gnome-software
Sep 24 11:16:25 proto kernel: [11906]  3169 11906   121657        0      77     8087             0 tracker-store
Sep 24 11:16:25 proto kernel: [12100]  3169 12100 25467586        0     318     3787             0 evolution-calen
Sep 24 11:16:25 proto kernel: [12105]  3169 12105    49663        0      32      189             0 ibus-engine-sim
Sep 24 11:16:25 proto kernel: [12141]  3169 12141    46920        0      27      711             0 dconf-service
Sep 24 11:16:25 proto kernel: [12169]  3169 12169    54896        0      43     1200             0 gvfsd-metadata
Sep 24 11:16:25 proto kernel: [12203]  3169 12203 25572290        0     316     2891             0 evolution-calen
Sep 24 11:16:25 proto kernel: [12229]  3169 12229 25463908        0     313     2247             0 evolution-addre
Sep 24 11:16:25 proto kernel: [12270]  3169 12270 29710767        0     315     2320             0 evolution-addre
Sep 24 11:16:25 proto kernel: [14301]  3169 14301  2614730    39590     972   105233             0 firefox
Sep 24 11:16:25 proto kernel: [14480]  3169 14480   833770   107495    1172    98993             0 Web Content
Sep 24 11:16:25 proto kernel: [14515]  3169 14515    22106       29      44      157             0 gconfd-2
Sep 24 11:16:25 proto kernel: [14666]  3169 14666  2994066  1437441    5414   971834             0 Web Content
Sep 24 11:16:25 proto kernel: [15894]     0 15894   172319     1037      77     3473             0 glusterfs
Sep 24 11:16:25 proto kernel: [16008]  3169 16008    51631       12      32      306             0 oosplash
Sep 24 11:16:25 proto kernel: [16035]  3169 16035   609683    20202     566    52404             0 soffice.bin
Sep 24 11:16:25 proto kernel: [16695]  3169 16695   836623    34489    1135   160254             0 Web Content
Sep 24 11:16:25 proto kernel: [18397]  3169 18397   828987    59395    1179   160001             0 Web Content
Sep 24 11:16:25 proto kernel: [21266]     0 21266   173567     2592      81     4658             0 glusterfs
Sep 24 11:16:25 proto kernel: [21489]  3169 21489   437863     3970     218    11824             0 nautilus
Sep 24 11:16:25 proto kernel: [21491]  3169 21491   255634     1673     165     3605             0 gnome-terminal-
Sep 24 11:16:25 proto kernel: [21505]  3169 21505     5231        2      13       45             0 gnome-pty-helpe
Sep 24 11:16:25 proto kernel: [21507]  3169 21507     6674        2      16      281             0 tcsh
Sep 24 11:16:25 proto kernel: [22214]     0 22214   195871    32951     158    12853             0 glusterfs
Sep 24 11:16:25 proto kernel: [22252]  3169 22252     6674        2      15      281             0 tcsh
Sep 24 11:16:25 proto kernel: [22551]  3169 22551   353445     2375     578   161038             0 python
Sep 24 11:16:25 proto kernel: [25213]  3169 25213     6674        1      17      280             0 tcsh
Sep 24 11:16:25 proto kernel: [25262]  3169 25262   337219      250     440    22571             0 python
Sep 24 11:16:25 proto kernel: [25415]  3169 25415    11252        0      21      131             0 dbus-daemon
Sep 24 11:16:26 proto kernel: [25416]  3169 25416    28361       74      13       71             0 bash
Sep 24 11:16:26 proto kernel: [25788]  3169 25788   123937     2810     191     7997             0 casaviewer
Sep 24 11:16:26 proto kernel: [25789]  3169 25789    28361       74      15       71             0 bash
Sep 24 11:16:26 proto kernel: [ 4519]  3169  4519     6778        2      16      379             0 tcsh
Sep 24 11:16:26 proto kernel: [  589]  3169   589    55786        3      93      626             0 kdeinit4
Sep 24 11:16:26 proto kernel: [  593]  3169   593    64962        2     105      800             0 klauncher
Sep 24 11:16:26 proto kernel: [  595]  3169   595   111974      123     192     1692             0 kded4
Sep 24 11:16:26 proto kernel: [  601]  3169   601     6683        2      16       62             0 gam_server
Sep 24 11:16:26 proto kernel: [ 3273]  3169  3273   111241      651     190     1164             0 kuiserver
Sep 24 11:16:26 proto kernel: [16172]  3169 16172    18106        0      38      195             0 ssh-agent
Sep 24 11:16:26 proto kernel: [ 6784]  3169  6784   117255        0      49      281             0 gvfsd-network
Sep 24 11:16:26 proto kernel: [ 6834]  3169  6834   123387       21      59      243             0 gvfsd-dnssd
Sep 24 11:16:26 proto kernel: [17507]    89 17507    25501       15      47      240             0 pickup
Sep 24 11:16:26 proto kernel: [28782]     0 28782    27687      131      53        0             0 sshd
Sep 24 11:16:26 proto kernel: [28788]     0 28788    28891       91      12       22             0 ksmtuned
Sep 24 11:16:26 proto kernel: [28795]     0 28795    27526       33      10        0             0 agetty
Sep 24 11:16:26 proto kernel: [28802]     0 28802    28378       50      13        0             0 awk
Sep 24 11:16:26 proto kernel: [28803]  3169 28803    26996       57      11        0             0 sleep
Sep 24 11:16:26 proto kernel: Out of memory: Kill process 14666 (Web Content) score 598 or sacrifice child
Sep 24 11:16:26 proto kernel: Killed process 14666 (Web Content) total-vm:11976264kB, anon-rss:5749764kB, file-rss:0kB, shmem-rss:0kB
Sep 24 11:19:05 proto journal: JS ERROR: Error: value is out of range for Argument 'n' (type guint64)#012ngettext@resource:///org/gnome/gjs/modules/gettext.js:65:12#012description@resource:///org/gnome/shell/ui/endSessionDialog.js:87:16#012_sync@resource:///org/gnome/shell/ui/endSessionDialog.js:455:27#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Sep 24 11:19:05 proto journal: JS ERROR: Error: value is out of range for Argument 'n' (type guint64)#012ngettext@resource:///org/gnome/gjs/modules/gettext.js:65:12#012description@resource:///org/gnome/shell/ui/endSessionDialog.js:87:16#012_sync@resource:///org/gnome/shell/ui/endSessionDialog.js:455:27#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Sep 24 11:19:08 proto journal: Timeout was reached
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor941
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor942
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor943
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor929
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor944
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor945
Sep 24 11:19:09 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor946
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor947
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor948
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor949
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor930
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor931
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor932
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor933
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor934
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor935
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor936
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor937
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor938
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor939
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor952
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor950
Sep 24 11:19:10 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor951
Sep 24 11:19:11 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor955
Sep 24 11:19:11 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor953
Sep 24 11:19:11 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor954
Sep 24 11:19:11 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor956
Sep 24 11:19:11 proto journal: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor940
Sep 24 11:19:13 proto systemd-logind: Delay lock is active (UID <removed>, PID <removed>) but inhibitor timeout is reached.
Sep 24 11:19:13 proto systemd-logind: System is powering down.
Sep 24 11:19:15 proto systemd: Stopping Session c2 of user gdm.
Sep 24 11:20:25 proto kernel: Initializing cgroup subsys cpuset
Sep 24 11:20:25 proto kernel: Initializing cgroup subsys cpu
Sep 24 11:20:25 proto kernel: Initializing cgroup subsys cpuacct
Sep 24 11:20:25 proto kernel: Linux version 3.10.0-957.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 8 23:39:32 UTC 2018
Sep 24 11:20:25 proto kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-957.el7.x86_64 <removed>
I've hidden some info in the log there, marked by <removed>, just in case.

The machine physically clicked when the reboot happened. This is the most info /var/log/messages has shown around the issue so far. I don't typically see an OOM killer prior to the reboot, this is the first time that has happened. Ditto for the GNOME messages.

To stress, this is the first time it has happened on CentOS 7. All the instances on CentOS 6 did not show the "System is powering down" message.

Does anyone have any advice here?

Cheers,
CD

aks
Posts: 2999
Joined: 2014/09/20 11:22:14

Re: Workstation Uninstructed Reboot

Post by aks » 2019/09/29 07:42:29

Reduce the number of programs running at the same time.
Add RAM.
Add swap.
Not much else you can do.

desertcat
Posts: 760
Joined: 2014/08/07 02:17:29
Location: Tucson, AZ

Re: Workstation Uninstructed Reboot

Post by desertcat » 2019/09/29 09:15:02

CaveDann wrote:
2019/09/25 10:14:54

I'll provide as much info as I can on this. I'm not particularly well versed in dealing with error logs though so forgive me if I'm not performing otherwise obvious steps.

Over the past 6 months, one of my PC's has been randomly rebooting itself without being instructed to do so. This has happened on all of CentOS 6.6, 6.7, 6.9 and now 7.6 too. Posting to CentOS 7 General as 7 is the desired OS for this PC.

Throughout using CentOS 6, no error logs were produced as part of this process. Simply, the logs would show that the machine was operating normally, then log that the kernal was being initialised as the system powered back up.

Now in CentOS 7.6, /var/log/messages is recording some additional information.

[snip]

Sep 24 11:09:18 proto gnome-keyring-daemon[10802]: dbus failure responding to ending session: Timeout was reached
Sep 24 11:09:36 proto journal: Failed to call Shutdown on session manager: Timeout was reached
Sep 24 11:16:16 proto kernel: accounts-daemon invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
Sep 24 11:16:16 proto kernel: accounts-daemon cpuset=/ mems_allowed=0
Sep 24 11:16:16 proto kernel: CPU: 0 PID: 3631 Comm: accounts-daemon Kdump: loaded Not tainted 3.10.0-957.el7.x86_64 #1
Sep 24 11:16:16 proto kernel: Hardware name: Dell Inc. Precision 3630 Tower/0NNNCT, BIOS 1.1.6 12/14/2018
Sep 24 11:16:17 proto kernel: Call Trace:

[snip]

Sep 24 11:16:26 proto kernel: Out of memory: Kill process 14666 (Web Content) score 598 or sacrifice child
Sep 24 11:16:26 proto kernel: Killed process 14666 (Web Content) total-vm:11976264kB, anon-rss:5749764kB, file-rss:0kB, shmem-rss:0kB
Sep 24 11:19:05 proto journal: JS ERROR: Error: value is out of range for Argument 'n' (type guint64)#012ngettext@resource:///org/gnome/gjs/modules/gettext.js:65:12#012description@resource:///org/gnome/shell/ui/endSessionDialog.js:87:16#012_sync@resource:///org/gnome/shell/ui/endSessionDialog.js:455:27#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Sep 24 11:19:05 proto journal: JS ERROR: Error: value is out of range for Argument 'n' (type guint64)#012ngettext@resource:///org/gnome/gjs/modules/gettext.js:65:12#012description@resource:///org/gnome/shell/ui/endSessionDialog.js:87:16#012_sync@resource:///org/gnome/shell/ui/endSessionDialog.js:455:27#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22

[snip]

The machine physically clicked when the reboot happened. This is the most info /var/log/messages has shown around the issue so far. I don't typically see an OOM killer prior to the reboot, this is the first time that has happened. Ditto for the GNOME messages.

To stress, this is the first time it has happened on CentOS 7. All the instances on CentOS 6 did not show the "System is powering down" message.

Does anyone have any advice here?

Cheers,
CD
OK before we do anything let's try and logically figure things out:

First confirm if your machine is a Dell Inc. Precision 3630 Tower. If so how much RAM does it have? Is it 16 GB of DDR4 RAM or 32GB of DDR4 RAM? If you have 16GB of RAM you have more than enough RAM.

Does it have an Intel 7th Gen 6 core CPU? Correct?

When you installed CentOS 7 how much SWAP did you allocate? 4GB should be more than enough, and 6-8GB Is a good Safety Factor. If you have <= 4GB that might be the problem, but I am a bit dubious about that.

No, I am leaning towards something different. You say you have an "Uninstructed Reboot". This leads me to suspect you *may* have a power problem. So let's check something: Do you have the machine plugged into a UPS (Uninterruptible Power Supply ), or just a surge protector??

Here is my *guess* based on what little I know: You have DIRTY power, and you do not have the machine set up to shutdown and stay down if your power fails. Ergo, if you get a hiccup in your power it is enough to briefly power OFF the Machine, leading to an almost Instantaneous Reboot. Most surge protectors are woefully insufficient for when you have a 600-800W power supply. They were great when the IBM PC came out, they were great even when power supplies got up to 150W, but baby those were the Good Ol' Days. My WS, Gateway, Backup machine, and Test Bed, plus dual monitors are plugged into a pair of "Patriot 425" UPS's Should I lose power totally, I have 5 minutes to do an orderly shut down of everything; should I lose power while I am asleep when the computers shutdown, they stay down, until I re-boot them in the morning. In the 10-15 years I have had them I think I have only woken up to a dead computer 4 times, and had prolonged power outages of more than a few seconds only about 6 times, where I had to actually start shutting down all the machines.

If you have a UPS when was the last time you changed the Batteries? A set of Batteries *should* last 2-4 years. If the UPS starts feeling WARM or even HOT it is time to change the Batteries.

If you have your WS plugged into a UPS, and the Batteries are relatively new, then I don't have a clue what is going on; OTOH if you don't have it plugged into a UPS maybe it would be worth your while to consider investing in one. In the meantime check your settings so that once the machine loses power it does not re-boot when the power comes back on.

Sincerely,
D'Cat

tony_down_under
Posts: 83
Joined: 2019/08/07 01:50:24
Location: Perth, Australia but originally from Carshalton, Surrey

Re: Workstation Uninstructed Reboot

Post by tony_down_under » 2019/10/02 07:29:27

Sep 24 11:16:26 proto kernel: Out of memory: Kill process 14666 (Web Content) score 598 or sacrifice child
aks wrote:
2019/09/29 07:42:29
Reduce the number of programs running at the same time.
Add RAM.
Add swap.
Not much else you can do.
Sep 24 11:16:26 proto kernel: Out of memory: Kill process 14666 (Web Content) score 598 or sacrifice child <- this, but not really an option :lol:

OP - logs are saying out of memory and your process was killed. Can you monitor your mem and swap usage and see if it's related to the issue you have?

CaveDann
Posts: 23
Joined: 2018/12/14 15:05:27
Location: UK

Re: Workstation Uninstructed Reboot

Post by CaveDann » 2019/10/04 14:10:44

Hey D'Cat, Tony,

Thanks for the response and apologies for the delayed reply.
desertcat wrote:
2019/09/29 09:15:02
First confirm if your machine is a Dell Inc. Precision 3630 Tower. If so how much RAM does it have? Is it 16 GB of DDR4 RAM or 32GB of DDR4 RAM? If you have 16GB of RAM you have more than enough RAM.

Does it have an Intel 7th Gen 6 core CPU? Correct?
Yes it's a P3630 Tower. It has 8GB DDR4 RAM installed. It has a quad-core coffee lake CPU.
desertcat wrote:
2019/09/29 09:15:02
When you installed CentOS 7 how much SWAP did you allocate? 4GB should be more than enough, and 6-8GB Is a good Safety Factor. If you have <= 4GB that might be the problem, but I am a bit dubious about that.
Its got 8GB SWAP allocated to it.
desertcat wrote:
2019/09/29 09:15:02
No, I am leaning towards something different. You say you have an "Uninstructed Reboot". This leads me to suspect you *may* have a power problem. So let's check something: Do you have the machine plugged into a UPS (Uninterruptible Power Supply ), or just a surge protector??

Here is my *guess* based on what little I know: You have DIRTY power, and you do not have the machine set up to shutdown and stay down if your power fails. Ergo, if you get a hiccup in your power it is enough to briefly power OFF the Machine, leading to an almost Instantaneous Reboot.
The BIOS setting is for the machine to stay down after a power interruption. I've triple checked this. I've physically moved it so that we're using completely different power outlets too, but the problem follows it around.

My current idea is to leave the workstation in the BIOS menu for a month, maybe more, and see if it reboots during that time. If it does, it will indicate that it's likely a hardware fault. However, if it doesn't, it'll tell me nothing.
tony_down_under wrote:
2019/10/02 07:29:27
OP - logs are saying out of memory and your process was killed. Can you monitor your mem and swap usage and see if it's related to the issue you have?
Sar is set up to only log every 10 minutes. Of all the times this problem has occurred, a 10 minute window has never highlighted anything for us. It's always been whilst the workstation has been idling. No log indicates that a user was actively controlling the workstation at the time of the reboot, though users have been logged in.

Really at a loss with this one.

Cheers,
CD

desertcat
Posts: 760
Joined: 2014/08/07 02:17:29
Location: Tucson, AZ

Re: Workstation Uninstructed Reboot

Post by desertcat » 2019/10/05 22:59:19

CaveDann wrote:
2019/10/04 14:10:44
Hey D'Cat, Tony,

Thanks for the response and apologies for the delayed reply.
desertcat wrote:
2019/09/29 09:15:02
First confirm if your machine is a Dell Inc. Precision 3630 Tower. If so how much RAM does it have? Is it 16 GB of DDR4 RAM or 32GB of DDR4 RAM? If you have 16GB of RAM you have more than enough RAM.

Does it have an Intel 7th Gen 6 core CPU? Correct?
Yes it's a P3630 Tower. It has 8GB DDR4 RAM installed. It has a quad-core coffee lake CPU.
desertcat wrote:
2019/09/29 09:15:02
When you installed CentOS 7 how much SWAP did you allocate? 4GB should be more than enough, and 6-8GB Is a good Safety Factor. If you have <= 4GB that might be the problem, but I am a bit dubious about that.
Its got 8GB SWAP allocated to it.
desertcat wrote:
2019/09/29 09:15:02
No, I am leaning towards something different. You say you have an "Uninstructed Reboot". This leads me to suspect you *may* have a power problem. So let's check something: Do you have the machine plugged into a UPS (Uninterruptible Power Supply ), or just a surge protector??

Here is my *guess* based on what little I know: You have DIRTY power, and you do not have the machine set up to shutdown and stay down if your power fails. Ergo, if you get a hiccup in your power it is enough to briefly power OFF the Machine, leading to an almost Instantaneous Reboot.
The BIOS setting is for the machine to stay down after a power interruption. I've triple checked this. I've physically moved it so that we're using completely different power outlets too, but the problem follows it around.

My current idea is to leave the workstation in the BIOS menu for a month, maybe more, and see if it reboots during that time. If it does, it will indicate that it's likely a hardware fault. However, if it doesn't, it'll tell me nothing.
tony_down_under wrote:
2019/10/02 07:29:27
OP - logs are saying out of memory and your process was killed. Can you monitor your mem and swap usage and see if it's related to the issue you have?
Sar is set up to only log every 10 minutes. Of all the times this problem has occurred, a 10 minute window has never highlighted anything for us. It's always been whilst the workstation has been idling. No log indicates that a user was actively controlling the workstation at the time of the reboot, though users have been logged in.

Really at a loss with this one.

Cheers,
CD
The BIOS setting is for the machine to stay down after a power interruption. I've triple checked this.
GREAT!!!
I've physically moved it so that we're using completely different power outlets too, but the problem follows it around.
Hummmnm. If you have dirty power it will not be solved by moving it to a different power outlet. The question was "Do you have access to a UPS"? This still sounds like a "hiccup" in the power supply -- just enough to shut it down but then immediately re-boot. Maybe like in a "Brown Out" such as it goes into a LOG OUT rather than a SHUT DOWN mode.

If you were to say hit the power off button, if I recall, it will give you a list of 3 options: Logout, Shut down, Cancel, the default (the first choice) is LOGOUT, if there is no user input within 60 seconds it log the user out rather than shutdown the machine. You have to a BLACKOUT ie NO POWER to trip the automatic shutdown.

lightman47
Posts: 1151
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Workstation Uninstructed Reboot

Post by lightman47 » 2019/10/06 11:34:26

One additional thought - is the CPU fan running & clear?
Remember - importing/building packages will likely "byte you in the butt" come update time, long after you'd forgotten you did that! Use repos whenever possible.

User avatar
TrevorH
Forum Moderator
Posts: 28842
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Workstation Uninstructed Reboot

Post by TrevorH » 2019/10/06 12:06:48

Sep 24 11:19:13 proto systemd-logind: Delay lock is active (UID <removed>, PID <removed>) but inhibitor timeout is reached.
Sep 24 11:19:13 proto systemd-logind: System is powering down.
Googling those leads to https://www.freedesktop.org/software/sy ... .conf.html and I think it's doing that because you have IdleAction=poweroff in /etc/systemd/logind.conf and it thinks your system is idle because one of the processes that was killed was the one it was looking at to determine if the system was idle.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

desertcat
Posts: 760
Joined: 2014/08/07 02:17:29
Location: Tucson, AZ

Re: Workstation Uninstructed Reboot

Post by desertcat » 2019/10/06 20:54:57

TrevorH wrote:
2019/10/06 12:06:48
Sep 24 11:19:13 proto systemd-logind: Delay lock is active (UID <removed>, PID <removed>) but inhibitor timeout is reached.
Sep 24 11:19:13 proto systemd-logind: System is powering down.
Googling those leads to https://www.freedesktop.org/software/sy ... .conf.html and I think it's doing that because you have IdleAction=poweroff in /etc/systemd/logind.conf and it thinks your system is idle because one of the processes that was killed was the one it was looking at to determine if the system was idle.
Nice find TrevorH. OK just for FUN I went to /etc/systemd/logind.conf. Under

[Login]

Everything is commented out with a # in front of it. My IdleAction line reads #IdleAction=ignore rather than IdleAction=poweroff

The OP might want to go to /etc/systemd/logind.conf to see what if anything is no longer commented out.

CaveDann
Posts: 23
Joined: 2018/12/14 15:05:27
Location: UK

Re: Workstation Uninstructed Reboot

Post by CaveDann » 2019/10/07 09:57:14

Hey All,

Thanks again for the support on this.

I can confirm, all the fans are clear and running.

Also, my /etc/systemd/logind.conf still holds the default configuration. All lines are commented out, no lines have been added or edited. I know it's commented, so it wouldn't have an effect anyway, but for the sake of clarity the line in question reads #IdleAction=ignore.

Still, thanks for the suggestion. It wasn't a line I'd caught and googled before.

If I find anything else, I'll update here. If anyone has any other questions or ideas, they're obviously more than welcome!

Cheers,
CD

Post Reply

Return to “CentOS 7 - General Support”