unexpected reboot - 1 node, no cluster

V

vamp

Active Member
Jun 24, 2017
24
2
43
38
Hello there,

I use one node Proxmox, no cluster or anything else. I not install any external app on base system, it is a full clean install.

The system today is suddenly reboot. I found only this on syslog:

Bash: 
Oct 26 23:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:30:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:30:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:31:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:31:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:32:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:32:02 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:33:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:33:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:34:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:34:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:34:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:35:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:35:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:35:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:36:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:36:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:36:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:37:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:37:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:37:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:38:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:38:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:38:02 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:39:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:39:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:39:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:40:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:40:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:41:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:41:02 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:42:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:42:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:43:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:43:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:44:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:44:02 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:45:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:45:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:46:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:46:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:47:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:47:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:47:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:48:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:48:01 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:48:01 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:49:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 26 23:49:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 26 23:49:02 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:51:18 pve systemd-modules-load[374]: Inserted module 'iscsi_tcp'
Oct 26 23:51:18 pve dmeventd[398]: dmeventd ready for processing.
Oct 26 23:51:18 pve systemd-modules-load[374]: Inserted module 'ib_iser'
Oct 26 23:51:18 pve kernel: [    0.000000] Linux version 5.4.65-1-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.65-1 (Mon, 21 Sep 2020 15:40:22 +0200) ()
Oct 26 23:51:18 pve systemd-tmpfiles[391]: [/usr/lib/tmpfiles.d/zabbix-agent.conf:1] Line references path below legacy directory /var/run/, updating /var/run/zabbix → /run/zabbix; please update the tmpfiles.d/ drop-in file accordingly.
Oct 26 23:51:18 pve kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.65-1-pve root=/dev/mapper/pve-root ro quiet
Oct 26 23:51:18 pve kernel: [    0.000000] KERNEL supported cpus:
Oct 26 23:51:18 pve systemd-modules-load[374]: Inserted module 'vhost_net'
Oct 26 23:51:18 pve kernel: [    0.000000]   Intel GenuineIntel
Oct 26 23:51:18 pve kernel: [    0.000000]   AMD AuthenticAMD

It happen rarely (once every two or three months) but i dont know why. I replaced system disk (new SSD) and replace the memory. i not see any overheat or overload on logs.

I dont know it help or not but i see this on syslog after reboot:

Bash: 
Oct 26 23:51:18 pve kernel: [    0.193492] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
Oct 26 23:51:18 pve kernel: [    0.193775] Freeing SMP alternatives memory: 40K
Oct 26 23:51:18 pve kernel: [    0.304089] smpboot: CPU0: Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz (family: 0x6, model: 0x3d, stepping: 0x4)
Oct 26 23:51:18 pve systemd[1]: Started Daily PVE download activities.
Oct 26 23:51:18 pve kernel: [    0.304187] mce: [Hardware Error]: Machine check events logged
Oct 26 23:51:18 pve kernel: [    0.304189] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: be00000000800400
Oct 26 23:51:18 pve kernel: [    0.304194] mce: [Hardware Error]: TSC 0 ADDR e000000000000000 MISC ffffffff80e76ffd
Oct 26 23:51:18 pve kernel: [    0.304199] mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1603752669 SOCKET 0 APIC 0 microcode 16
Oct 26 23:51:18 pve systemd[1]: Started Proxmox VE replication runner.
Oct 26 23:51:18 pve kernel: [    0.304244] Performance Events: PEBS fmt2+, Broadwell events, 16-deep LBR, full-width counters, Intel PMU driver.
Oct 26 23:51:18 pve kernel: [    0.304264] ... version:                3
Oct 26 23:51:18 pve systemd[1]: Started Daily apt upgrade and clean activities.
Oct 26 23:51:18 pve kernel: [    0.304264] ... bit width:              48
Oct 26 23:51:18 pve kernel: [    0.304265] ... generic registers:      4
Oct 26 23:51:18 pve kernel: [    0.304265] ... value mask:             0000ffffffffffff
Oct 26 23:51:18 pve kernel: [    0.304266] ... max period:             00007fffffffffff
Oct 26 23:51:18 pve systemd[1]: Started Daily man-db regeneration.
Oct 26 23:51:18 pve kernel: [    0.304267] ... fixed-purpose events:   3
Oct 26 23:51:18 pve kernel: [    0.304267] ... event mask:             000000070000000f
Oct 26 23:51:18 pve kernel: [    0.304308] rcu: Hierarchical SRCU implementation.
Oct 26 23:51:18 pve kernel: [    0.305278] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Oct 26 23:51:18 pve kernel: [    0.305346] smp: Bringing up secondary CPUs ...
Oct 26 23:51:18 pve systemd[1]: Started Daily rotation of log files.
Oct 26 23:51:18 pve kernel: [    0.305451] x86: Booting SMP configuration:
Oct 26 23:51:18 pve kernel: [    0.305452] .... node  #0, CPUs:      #1
Oct 26 23:51:18 pve systemd[1]: Reached target Timers.
Oct 26 23:51:18 pve kernel: [    0.305877] mce: [Hardware Error]: Machine check events logged
Oct 26 23:51:18 pve kernel: [    0.305879] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: be00000000800400
Oct 26 23:51:18 pve systemd[1]: Started PVE Qemu Event Daemon.
Oct 26 23:51:18 pve kernel: [    0.305883] mce: [Hardware Error]: TSC 0 ADDR e000000000000000 MISC ffffffff80e76ffd
Oct 26 23:51:18 pve kernel: [    0.305888] mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1603752669 SOCKET 0 APIC 2 microcode 16
Oct 26 23:51:18 pve kernel: [    0.305893]  #2
Oct 26 23:51:18 pve kernel: [    0.305893] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Oct 26 23:51:18 pve lxcfs[659]: Running constructor lxcfs_init to reload liblxcfs
Oct 26 23:51:18 pve kernel: [    0.305893]  #3
Oct 26 23:51:18 pve kernel: [    0.305893] smp: Brought up 1 node, 4 CPUs
 
Last edited:
The mce: [Hardware Error]: Machine check events logged lines seem to indicate a hardware problem with the CPU (or potentially the mainboard). Not much more detail than that though.

Other than that, nothing stands out from the logs...
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom