Proxmox VE auto reboot

[hoanglm]

My server auto reboot, any one tell me how to check why server reboot?
I have attached syslog and pveversion files below.
Thank all!

 

[Dunuin]

Did you check for hareware problems like running memtest86+ and replacing the PSU?
Didn`t see an error in the syslog right before the booting.

 

[janssensm]

You are also running PVE 6.x which is EOL:
https://pve.proxmox.com/wiki/FAQ#faq-support-table

Better you start planning your upgrade to 7.x.
Also, you don't seem to have installed intel-microcode. That can be a consious choice, but then you also accept some vulnerabilities not handled, and also maybe some functional fixes in the cpu.

 

[hoanglm]

There are some error logs like the following that coincide with the time when pve was rebooted, is this the cause of this situation?

Line 7865: Jul 7 15:19:52 pro kernel: [ 3.566943] ERST: Error Record Serialization Table (ERST) support is initialized.
Line 7903: Jul 7 15:19:52 pro kernel: [ 3.635368] RAS: Correctable Errors collector initialized.
Line 8246: Jul 7 15:19:52 pro kernel: [ 8.381657] EXT4-fs (dm-10): re-mounted. Opts: errors=remount-ro
Line 8252: Jul 7 15:19:52 pro kernel: [ 8.494827] ACPI Error: No handler for Region [SYSI] (0000000021fb728d) [IPMI] (20190816/evregion-134)
Line 8253: Jul 7 15:19:52 pro kernel: [ 8.494930] ACPI Error: Region IPMI (ID=7) has no handler (20190816/exfldio-265)
Line 8256: Jul 7 15:19:52 pro kernel: [ 8.495026] ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20190816/psparse-531)
Line 8256: Jul 7 15:19:52 pro kernel: [ 8.495026] ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20190816/psparse-531)
Line 8257: Jul 7 15:19:52 pro kernel: [ 8.495132] ACPI Error: Aborting method \_SB.PMI0._PMC due to previous error (AE_NOT_EXIST) (20190816/psparse-531)
Line 8257: Jul 7 15:19:52 pro kernel: [ 8.495132] ACPI Error: Aborting method \_SB.PMI0._PMC due to previous error (AE_NOT_EXIST) (20190816/psparse-531)
Line 8258: Jul 7 15:19:52 pro kernel: [ 8.495238] ACPI Error: AE_NOT_EXIST, Evaluating _PMC (20190816/power_meter-743)
Line 9648: Jul 7 15:44:58 pro systemd[8225]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Line 9673: Jul 7 15:46:38 pro systemd[8577]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Line 9745: Jul 7 15:49:55 pro systemd[9288]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Line 9870: Jul 7 16:01:35 pro systemd[11568]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Line 9899: Jul 7 16:03:46 pro systemd[12031]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed

 

[janssensm]

Nope, these log entries seem normal, these are boot messages.
Many systems generate ACPI errors, you could look if a more recent bios is available and flash it.
The last 5 lines can you can get rid of by installing apt install scdaemon
But still you should read my last advice.

If you are running an unsupported version, you will get less help on the forum too. So better to plan the upgrade and see how it runs.