Reboot occurs randomly

A

abc605521864

New Member
Dec 21, 2022
8
0
1
Hi, I have been suffering from random restarts of pve for months now, I don't see any errors in the syslog, the restarts happen at random times, sometimes just a few days, sometimes longer time, what should i do? thanks


Code: 
Dec 21 16:46:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:46:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:46:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:47:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:47:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:47:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:48:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:48:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:48:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:49:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:49:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:49:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:50:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:50:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:50:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:51:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:51:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:51:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:52:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:52:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:52:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:53:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:53:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:53:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:54:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:54:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:54:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:55:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:55:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:55:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:56:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:56:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:56:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:57:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:57:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:57:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:58:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:58:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:58:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 16:59:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 16:59:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 16:59:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:00:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:00:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:00:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:01:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:01:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:01:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:02:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:02:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:02:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:03:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:03:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:03:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:04:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:04:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:04:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:05:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:05:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:05:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:06:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:06:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:06:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:07:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:07:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:07:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:08:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:08:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:08:01 node0 systemd[1]: Finished Proxmox VE replication runner.
Dec 21 17:09:00 node0 systemd[1]: Starting Proxmox VE replication runner...
Dec 21 17:09:01 node0 systemd[1]: pvesr.service: Succeeded.
Dec 21 17:09:01 node0 systemd[1]: Finished Proxmox VE replication runner.
-- Reboot --
Dec 21 17:10:43 node0 kernel: Linux version 5.11.22-4-pve (build@proxmox) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP PVE 5.11.22-8~bpo10+1 (Thu, 09 Sep 2021 12:52:26 +0200) ()
Dec 21 17:10:43 node0 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.22-4-pve root=/dev/mapper/pve-root ro quiet
Dec 21 17:10:43 node0 kernel: KERNEL supported cpus:
Dec 21 17:10:43 node0 kernel:   Intel GenuineIntel
Dec 21 17:10:43 node0 kernel:   AMD AuthenticAMD
Dec 21 17:10:43 node0 kernel:   Hygon HygonGenuine
Dec 21 17:10:43 node0 kernel:   Centaur CentaurHauls
Dec 21 17:10:43 node0 kernel:   zhaoxin   Shanghai
Dec 21 17:10:43 node0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dec 21 17:10:43 node0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dec 21 17:10:43 node0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dec 21 17:10:43 node0 kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Dec 21 17:10:43 node0 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Dec 21 17:10:43 node0 kernel: x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
Dec 21 17:10:43 node0 kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Dec 21 17:10:43 node0 kernel: BIOS-provided physical RAM map:
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009cfefff] usable
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x0000000009cff000-0x0000000009ffffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x000000000a20e000-0x00000000c9fd3fff] usable
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000c9fd4000-0x00000000ca3dcfff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000ca3dd000-0x00000000ca53ffff] ACPI data
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000ca540000-0x00000000cac75fff] ACPI NVS
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000cac76000-0x00000000cb945fff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000cb946000-0x00000000cb9fefff] type 20
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000cb9ff000-0x00000000ccffffff] usable
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000cd000000-0x00000000cfffffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fd400000-0x00000000fd5fffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000202f2fffff] usable
Dec 21 17:10:43 node0 kernel: BIOS-e820: [mem 0x000000202f300000-0x000000202fffffff] reserved
Dec 21 17:10:43 node0 kernel: NX (Execute Disable) protection: active
Dec 21 17:10:43 node0 kernel: efi: EFI v2.70 by American Megatrends
Dec 21 17:10:43 node0 kernel: efi: ACPI=0xca53f000 ACPI 2.0=0xca53f014 TPMFinalLog=0xcac29000 SMBIOS=0xcb7eb000 SMBIOS 3.0=0xcb7ea000 MEMATTR=0xc842f698 ESRT=0xc8acfb98
Dec 21 17:10:43 node0 kernel: secureboot: Secure boot could not be determined (mode 0)
Dec 21 17:10:43 node0 kernel: SMBIOS 3.3.0 present.
Dec 21 17:10:43 node0 kernel: DMI: ASUS System Product Name/Pro WS X570-ACE, BIOS 3801 07/30/2021

Code: 
reboot   system boot  5.11.22-4-pve    Wed Dec 21 17:10   still running
reboot   system boot  5.11.22-4-pve    Mon Oct 31 15:15   still running
reboot   system boot  5.11.22-4-pve    Fri Sep  9 13:14   still running
reboot   system boot  5.11.22-4-pve    Thu Sep  1 23:22   still running
reboot   system boot  5.11.22-4-pve    Fri Jul 29 20:58   still running
reboot   system boot  5.11.22-4-pve    Thu Jul 28 12:34   still running
reboot   system boot  5.11.22-4-pve    Tue Jul  5 21:59   still running
reboot   system boot  5.11.22-4-pve    Sun Jun 19 13:08   still running
reboot   system boot  5.11.22-4-pve    Wed Mar 23 11:23   still running
reboot   system boot  5.11.22-4-pve    Thu Mar 17 12:58   still running
reboot   system boot  5.11.22-4-pve    Thu Mar 10 14:34   still running
reboot   system boot  5.11.22-4-pve    Wed Feb  2 09:02   still running
reboot   system boot  5.11.22-4-pve    Sat Jan  1 14:15   still running
 
I would start with updating the bios/UEFI and all firmwares if any and especially the PVE itself...
 
Neobin said:
So you pinned that kernel?
What is the full output of: pveversion -v

PS.: Per default, there is no automatic update...
Click to expand...
:oops:The prompt I see in Updates is: No update available
Code: 
proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-7~bpo10+1
pve-kernel-helper: 7.0-3
pve-kernel-5.11.22-4-pve: 5.11.22-8~bpo10+1
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-5
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-7
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1~bpo10+1
updates.png
 
Most likely because you do not have configured a appropriate PVE-repository.

If you do not have an active subscription: [1], you need to:
  1. Disable/Comment out the pve-enterprise repository: [2] (See the note there)
  2. Add the pve-no-subscription repository: [3]
  3. Update: [4] the PVE-host
  4. Reboot the PVE-host

[1] https://proxmox.com/en/proxmox-ve/pricing
[2] https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo
[3] https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo
[4] https://pve.proxmox.com/wiki/System_Software_Updates
 
Neobin said:
Most likely because you do not have configured a appropriate PVE-repository.

If you do not have an active subscription: [1], you need to:
  1. Disable/Comment out the pve-enterprise repository: [2] (See the note there)
  2. Add the pve-no-subscription repository: [3]
  3. Update: [4] the PVE-host
  4. Reboot the PVE-host

[1] https://proxmox.com/en/proxmox-ve/pricing
[2] https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo
[3] https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo
[4] https://pve.proxmox.com/wiki/System_Software_Updates
Click to expand...
ok, thanks for your reply:D
 
Neobin said:
Most likely because you do not have configured a appropriate PVE-repository.

If you do not have an active subscription: [1], you need to:
  1. Disable/Comment out the pve-enterprise repository: [2] (See the note there)
  2. Add the pve-no-subscription repository: [3]
  3. Update: [4] the PVE-host
  4. Reboot the PVE-host

[1] https://proxmox.com/en/proxmox-ve/pricing
[2] https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo
[3] https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo
[4] https://pve.proxmox.com/wiki/System_Software_Updates
Click to expand...
hi~ I still encounter the same problem after doing these operations:(
Code: 
Dec 25 11:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 81 to 80
Dec 25 11:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 79 to 72
Dec 25 12:13:54 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 72 to 73
Dec 25 12:17:01 node0 CRON[2535283]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 12:17:01 node0 CRON[2535290]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 12:17:01 node0 CRON[2535283]: pam_unix(cron:session): session closed for user root
Dec 25 12:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 80 to 79
Dec 25 12:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 73 to 79
Dec 25 13:17:01 node0 CRON[259738]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 13:17:01 node0 CRON[259751]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 13:17:01 node0 CRON[259738]: pam_unix(cron:session): session closed for user root
Dec 25 14:13:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 79 to 77
Dec 25 14:17:01 node0 CRON[2167083]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 14:17:01 node0 CRON[2167084]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 14:17:01 node0 CRON[2167083]: pam_unix(cron:session): session closed for user root
Dec 25 14:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 79 to 78
Dec 25 14:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 71
Dec 25 15:13:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 79
Dec 25 15:17:01 node0 CRON[3886814]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 15:17:01 node0 CRON[3886815]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 15:17:01 node0 CRON[3886814]: pam_unix(cron:session): session closed for user root
Dec 25 15:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 79 to 78
Dec 25 15:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 71 to 74
Dec 25 16:13:54 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 76
Dec 25 16:13:54 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 75
Dec 25 16:17:01 node0 CRON[1270191]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 16:17:01 node0 CRON[1270192]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 16:17:01 node0 CRON[1270191]: pam_unix(cron:session): session closed for user root
Dec 25 16:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 76 to 77
Dec 25 16:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 75 to 69
Dec 25 17:13:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 76
Dec 25 17:13:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 69 to 68
Dec 25 17:17:01 node0 CRON[3442022]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 17:17:01 node0 CRON[3442026]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 17:17:01 node0 CRON[3442022]: pam_unix(cron:session): session closed for user root
Dec 25 17:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 76 to 78
Dec 25 17:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 68 to 77
Dec 25 18:13:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 77 to 75
Dec 25 18:17:01 node0 CRON[701035]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 18:17:01 node0 CRON[701036]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 18:17:01 node0 CRON[701035]: pam_unix(cron:session): session closed for user root
Dec 25 18:33:10 node0 kernel: traps: php-fpm[1534255] general protection fault ip:ae8e08 sp:7ffe606dce90 error:0 in php-fpm[400000+b4d000]
Dec 25 18:33:10 node0 kernel: traps: php-fpm[2802208] general protection fault ip:ae8e08 sp:7ffe606dce90 error:0 in php-fpm[400000+b4d000]
Dec 25 18:38:50 node0 kernel: traps: php-fpm[550426] general protection fault ip:ae8e08 sp:7ffe606dce90 error:0 in php-fpm[400000+b4d000]
Dec 25 18:43:54 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 75 to 74
Dec 25 19:13:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 71
Dec 25 19:14:15 node0 kernel: traps: php-fpm[2324225] general protection fault ip:ae8e08 sp:7ffe606dce90 error:0 in php-fpm[400000+b4d000]
Dec 25 19:14:15 node0 kernel: traps: php-fpm[108355] general protection fault ip:ae8e08 sp:7ffe606dce90 error:0 in php-fpm[400000+b4d000]
Dec 25 19:17:01 node0 CRON[2683859]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 25 19:17:01 node0 CRON[2683860]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 25 19:17:01 node0 CRON[2683859]: pam_unix(cron:session): session closed for user root
Dec 25 19:43:53 node0 smartd[4520]: Device: /dev/sdi [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 77
Dec 25 19:43:53 node0 smartd[4520]: Device: /dev/sdj [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 71 to 76
-- Reboot --
Dec 25 19:49:06 node0 kernel: Linux version 5.15.74-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.15.74-1 (Mon, 14 Nov 2022 20:17:15 +0100) ()
Dec 25 19:49:06 node0 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve root=/dev/mapper/pve-root ro quiet
Dec 25 19:49:06 node0 kernel: KERNEL supported cpus:
Dec 25 19:49:06 node0 kernel:   Intel GenuineIntel
Dec 25 19:49:06 node0 kernel:   AMD AuthenticAMD
Dec 25 19:49:06 node0 kernel:   Hygon HygonGenuine
Dec 25 19:49:06 node0 kernel:   Centaur CentaurHauls
Dec 25 19:49:06 node0 kernel:   zhaoxin   Shanghai
Dec 25 19:49:06 node0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dec 25 19:49:06 node0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dec 25 19:49:06 node0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dec 25 19:49:06 node0 kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Dec 25 19:49:06 node0 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Dec 25 19:49:06 node0 kernel: x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
Dec 25 19:49:06 node0 kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Dec 25 19:49:06 node0 kernel: signal: max sigframe size: 3376
Dec 25 19:49:06 node0 kernel: BIOS-provided physical RAM map:
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d1efff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x0000000009d1f000-0x0000000009ffffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x000000000a20e000-0x00000000c30fafff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000c30fb000-0x00000000c30fbfff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000c30fc000-0x00000000ca36dfff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000ca36e000-0x00000000ca774fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000ca775000-0x00000000ca8dafff] ACPI data
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000ca8db000-0x00000000cac57fff] ACPI NVS
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000cac58000-0x00000000cb945fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000cb946000-0x00000000cb9fefff] type 20
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000cb9ff000-0x00000000ccffffff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000cd000000-0x00000000cfffffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fd400000-0x00000000fd5fffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000202f2fffff] usable
Dec 25 19:49:06 node0 kernel: BIOS-e820: [mem 0x000000202f300000-0x000000202fffffff] reserved
Dec 25 19:49:06 node0 kernel: NX (Execute Disable) protection: active
Dec 25 19:49:06 node0 kernel: efi: EFI v2.70 by American Megatrends
Dec 25 19:49:06 node0 kernel: efi: ACPI=0xca8da000 ACPI 2.0=0xca8da014 TPMFinalLog=0xcac0b000 SMBIOS=0xcb7d9000 SMBIOS 3.0=0xcb7d8000 MEMATTR=0xc5c66698 ESRT=0xc645c818
Dec 25 19:49:06 node0 kernel: secureboot: Secure boot could not be determined (mode 0)
Dec 25 19:49:06 node0 kernel: SMBIOS 3.3.0 present.
Dec 25 19:49:06 node0 kernel: DMI: ASUS System Product Name/Pro WS X570-ACE, BIOS 4201 04/26/2022
 
Hi abc605521864,

Thanks for the prompt reply :).
I'm new to Linux and proxmox.

FYI, i don't have this problem but for knowledge's sake, can share how to clear overclock settings?
 
bond347 said:
Hi abc605521864,

Thanks for the prompt reply :).
I'm new to Linux and proxmox.

FYI, i don't have this problem but for knowledge's sake, can share how to clear overclock settings?
Click to expand...
You're welcome, I don't know much about this, maybe my cpu overclocking caused the cpu to encounter an error. About clearing the bios overclocking, maybe you can visit Google to get more detailed tutorials. There are many motherboard models of each brand and there are great differences. I can't help you, sorry.
 
Hi abc605521864,

Noted.
Anyway, congrats on resolving your mysterious server reboot problem :).
 
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
Back