【HELP! Random reboot in Proxmox server without loads】

[ps2pspgood]

Hi,
Recently, I encountered some random reboot in the proxmox server. I cannot figure out the problem...
Some times it can run nicely for 5 days, but some times it can only run for several hours before spontaneously rebooting.
I have frequently use 1 ubuntu container running AD guard home, 1 Ubuntu server for running some GPU heavy works and 1 windows 10 VM to run CPU heavy works. I only run container and each vm on same time. Ubuntu and windows vm are not used at the same time.
After I encounter this problem, I turned off all the resource heavy program to see if the reboot is coming again. I try it with windows server first. However, after 1 day, the reboot occurred...
Then, I tried Ubuntu server VM. Similarly, the reboot happened after some times.
The following log is the most recent reboot. I take some part of it.
Hopefully, you can help me to solve the problem.

Thank you very much for the great help.

Mar 04 00:00:12 Pakuchi-Tree telegraf[1651]: 2022-03-03T16:00:12Z E! [outputs.influxdb_v2] When writing to [https://us-east-1-1.aws.cloud2.influxdata.com]: Post "https://us-east-1-1.aws.cloud2.influxdata.com/api/v2/write?bucket=Pakuchi-tree&org=kazuki.cloud.server%40gmail.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Mar 04 00:00:12 Pakuchi-Tree telegraf[1651]: 2022-03-03T16:00:12Z E! [agent] Error writing to outputs.influxdb_v2: Post "https://us-east-1-1.aws.cloud2.influxdata.com/api/v2/write?bucket=Pakuchi-tree&org=kazuki.cloud.server%40gmail.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Mar 04 00:00:20 Pakuchi-Tree telegraf[1651]: 2022-03-03T16:00:20Z E! [outputs.influxdb_v2] When writing to [https://us-east-1-1.aws.cloud2.influxdata.com]: Post "https://us-east-1-1.aws.cloud2.influxdata.com/api/v2/write?bucket=Pakuchi-tree&org=kazuki.cloud.server%40gmail.com": read tcp 192.168.50.100:39300->34.196.233.7:443: read: connection reset by peer Mar 04 00:00:20 Pakuchi-Tree telegraf[1651]: 2022-03-03T16:00:20Z E! [agent] Error writing to outputs.influxdb_v2: Post "https://us-east-1-1.aws.cloud2.influxdata.com/api/v2/write?bucket=Pakuchi-tree&org=kazuki.cloud.server%40gmail.com": read tcp 192.168.50.100:39300->34.196.233.7:443: read: connection reset by peer Mar 04 00:00:20 Pakuchi-Tree systemd[1]: Starting Rotate log files... Mar 04 00:00:20 Pakuchi-Tree systemd[1]: Starting Daily man-db regeneration... Mar 04 00:00:20 Pakuchi-Tree systemd[1]: Reloading PVE API Proxy Server. Mar 04 00:00:20 Pakuchi-Tree systemd[1]: man-db.service: Succeeded. Mar 04 00:00:20 Pakuchi-Tree systemd[1]: Finished Daily man-db regeneration. Mar 04 00:00:20 Pakuchi-Tree pveproxy[1140418]: send HUP to 1967 Mar 04 00:00:20 Pakuchi-Tree pveproxy[1967]: received signal HUP Mar 04 00:00:20 Pakuchi-Tree pveproxy[1967]: server closing Mar 04 00:00:20 Pakuchi-Tree pveproxy[1967]: server shutdown (restart) Mar 04 00:00:20 Pakuchi-Tree systemd[1]: Reloaded PVE API Proxy Server. Mar 04 00:00:20 Pakuchi-Tree systemd[1]: Reloading PVE SPICE Proxy Server. Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1140421]: send HUP to 1973 Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1973]: received signal HUP Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1973]: server closing Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1973]: server shutdown (restart) Mar 04 00:00:21 Pakuchi-Tree systemd[1]: Reloaded PVE SPICE Proxy Server. Mar 04 00:00:21 Pakuchi-Tree pvefw-logger[596858]: received terminate request (signal) Mar 04 00:00:21 Pakuchi-Tree pvefw-logger[596858]: stopping pvefw logger Mar 04 00:00:21 Pakuchi-Tree systemd[1]: Stopping Proxmox VE firewall logger... Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1973]: restarting server Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1973]: starting 1 worker(s) Mar 04 00:00:21 Pakuchi-Tree spiceproxy[1973]: worker 1140429 started Mar 04 00:00:21 Pakuchi-Tree pveproxy[1967]: restarting server Mar 04 00:00:21 Pakuchi-Tree pveproxy[1967]: starting 3 worker(s) Mar 04 00:00:21 Pakuchi-Tree pveproxy[1967]: worker 1140430 started Mar 04 00:00:21 Pakuchi-Tree pveproxy[1967]: worker 1140431 started Mar 04 00:00:21 Pakuchi-Tree pveproxy[1967]: worker 1140432 started Mar 04 00:00:21 Pakuchi-Tree systemd[1]: pvefw-logger.service: Succeeded. Mar 04 00:00:21 Pakuchi-Tree systemd[1]: Stopped Proxmox VE firewall logger. Mar 04 00:00:21 Pakuchi-Tree systemd[1]: pvefw-logger.service: Consumed 5.144s CPU time. Mar 04 00:00:21 Pakuchi-Tree systemd[1]: Starting Proxmox VE firewall logger... Mar 04 00:00:21 Pakuchi-Tree pvefw-logger[1140434]: starting pvefw logger Mar 04 00:00:21 Pakuchi-Tree systemd[1]: Started Proxmox VE firewall logger. Mar 04 00:00:21 Pakuchi-Tree systemd[1]: rsyslog.service: Sent signal SIGHUP to main process 1478 (rsyslogd) on client request. Mar 04 00:00:21 Pakuchi-Tree systemd[1]: logrotate.service: Succeeded. Mar 04 00:00:21 Pakuchi-Tree systemd[1]: Finished Rotate log files. Mar 04 00:00:26 Pakuchi-Tree spiceproxy[596853]: worker exit Mar 04 00:00:26 Pakuchi-Tree spiceproxy[1973]: worker 596853 finished Mar 04 00:00:26 Pakuchi-Tree pveproxy[1128490]: worker exit Mar 04 00:00:26 Pakuchi-Tree pveproxy[1121664]: worker exit Mar 04 00:00:26 Pakuchi-Tree pveproxy[1121861]: worker exit Mar 04 00:00:26 Pakuchi-Tree pveproxy[1967]: worker 1121861 finished Mar 04 00:00:26 Pakuchi-Tree pveproxy[1967]: worker 1128490 finished Mar 04 00:00:26 Pakuchi-Tree pveproxy[1967]: worker 1121664 finished Mar 04 00:10:21 Pakuchi-Tree rsyslogd[1478]: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="1478" x-info="https://www.rsyslog.com"] rsyslogd was HUPed Mar 04 00:17:01 Pakuchi-Tree CRON[1146528]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 04 00:17:01 Pakuchi-Tree CRON[1146529]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 04 00:17:01 Pakuchi-Tree CRON[1146528]: pam_unix(cron:session): session closed for user root Mar 04 00:20:40 Pakuchi-Tree pvedaemon[1098489]: worker exit Mar 04 00:20:40 Pakuchi-Tree pvedaemon[1955]: worker 1098489 finished Mar 04 00:20:40 Pakuchi-Tree pvedaemon[1955]: starting 1 worker(s) Mar 04 00:20:40 Pakuchi-Tree pvedaemon[1955]: worker 1147937 started Mar 04 00:24:01 Pakuchi-Tree CRON[1149145]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 04 00:24:01 Pakuchi-Tree CRON[1149146]: (root) CMD (if [ $(date +%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/trim ]; then /usr/lib/zfs-linux/trim; fi) Mar 04 00:24:01 Pakuchi-Tree CRON[1149145]: pam_unix(cron:session): session closed for user root -- Reboot -- Mar 04 00:26:58 Pakuchi-Tree kernel: Linux version 5.13.19-4-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.13.19-9 (Mon, 07 Feb 2022 11:01:14 +0100) () Mar 04 00:26:58 Pakuchi-Tree kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.13.19-4-pve root=/dev/mapper/pve-root ro quiet amd_iommu=on iommu=pt pci-stub.ids=10de:2488,10de:228b video=efifb:off Mar 04 00:26:58 Pakuchi-Tree kernel: KERNEL supported cpus: Mar 04 00:26:58 Pakuchi-Tree kernel: Intel GenuineIntel Mar 04 00:26:58 Pakuchi-Tree kernel: AMD AuthenticAMD Mar 04 00:26:58 Pakuchi-Tree kernel: Hygon HygonGenuine Mar 04 00:26:58 Pakuchi-Tree kernel: Centaur CentaurHauls Mar 04 00:26:58 Pakuchi-Tree kernel: zhaoxin Shanghai Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers' Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8 Mar 04 00:26:58 Pakuchi-Tree kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format. Mar 04 00:26:58 Pakuchi-Tree kernel: BIOS-provided physical RAM map:

 

[Dunuin]

In case of system instabilities I always first test my RAM with memtest86+. Boot into a memtest86+ usb pen drive and let it run over night. If you don't see errors after about 8 hours the RAM should be fine. If the RAM is fine its very likely that the PSU has problems. So if a have a old PSU laying around I would switch it out and see if the problem is solved then.
If that still not fixed it I would upgrade the BIOS/UEFI. And if you can't find information in the syslog its sometimes useful to connect a keyboard/display to your server and look what you can see in the terminal while its crashing.