Random Shutdown on Proxmox.

[ylnest2018]

Getting random shutdown's on my Proxmox stack, I can't put it down to anything specifically as yet. Is there some way I can check what initiated the shutdown as I can see it was a sudden shutdown but an initiated one

 

[ylnest2018]

doesnt appear to be load related but I have a suspicion it could be due to reaching a high temp but have no way to tell

 

[gfngfn256]

Check log around that time with:

journalctl --since "2025-02-21 00:47:00" --until "2025-02-21 00:52:00"

 

[aabraham]

Getting random shutdown's on my Proxmox stack, I can't put it down to anything specifically as yet. Is there some way I can check what initiated the shutdown as I can see it was a sudden shutdown but an initiated one

View attachment 82685

What was happening inside that container and VM in that time?

 

[ylnest2018]

journalctl --since "2025-02-21 00:47:00" --until "2025-02-21 00:52:00"

He sorry for the delay I was unable to find time to run the command but I have now run the command above but tweaked to the time stamp, how am i best to share this, I will try upload as much as I can here but if its not easy to review please let me know the alternative.

Pretty weird it shows as the power button being pressed...when it wasnt

root@proxmox:~# journalctl --since "2025-02-21 12:26:00" --until "2025-02-21 12:32:00"
Feb 21 12:29:23 proxmox systemd-logind[990]: Power key pressed short.
Feb 21 12:29:23 proxmox systemd-logind[990]: Powering off...
Feb 21 12:29:23 proxmox systemd-logind[990]: System is powering down.
Feb 21 12:29:23 proxmox systemd[1]: 101.scope: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped 101.scope.
Feb 21 12:29:23 proxmox systemd[1]: 101.scope: Consumed 1d 21h 51min 28.595s CPU time.
Feb 21 12:29:23 proxmox systemd[1]: Removed slice qemu.slice - Slice /qemu.
Feb 21 12:29:23 proxmox systemd[1]: qemu.slice: Consumed 1d 21h 51min 28.595s CPU time.
Feb 21 12:29:23 proxmox systemd[1]: Removed slice system-modprobe.slice - Slice /system/modprobe.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target graphical.target - Graphical Interface.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target multi-user.target - Multi-User System.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target getty.target - Login Prompts.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target nut.target - Network UPS Tools - target for power device drivers, data server and monitoring client (if enabled) on this system.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target nut-driver.target - Network UPS Tools - target for power device drivers on this system.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target rpc_pipefs.target.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target rpcbind.target - RPC Port Mapper.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target sound.target - Sound Card.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target timers.target - Timer Units.
Feb 21 12:29:23 proxmox systemd[1]: apt-daily-upgrade.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
Feb 21 12:29:23 proxmox systemd[1]: apt-daily.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped apt-daily.timer - Daily apt download activities.
Feb 21 12:29:23 proxmox systemd[1]: dpkg-db-backup.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped dpkg-db-backup.timer - Daily dpkg database backup timer.
Feb 21 12:29:23 proxmox systemd[1]: e2scrub_all.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
Feb 21 12:29:23 proxmox systemd[1]: fstrim.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped fstrim.timer - Discard unused blocks once a week.
Feb 21 12:29:23 proxmox systemd[1]: logrotate.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped logrotate.timer - Daily rotation of log files.
Feb 21 12:29:23 proxmox systemd[1]: man-db.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped man-db.timer - Daily man-db regeneration.
Feb 21 12:29:23 proxmox systemd[1]: pve-daily-update.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped pve-daily-update.timer - Daily PVE download activities.
Feb 21 12:29:23 proxmox systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully.
Feb 21 12:29:23 proxmox systemd[1]: Stopped systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target zfs.target - ZFS startup target.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target zfs-import.target - ZFS pool import target.
Feb 21 12:29:23 proxmox systemd[1]: Stopped target zfs-volumes.target - ZFS volumes are ready.
Feb 21 12:29:23 proxmox systemd[1]: lvm2-lvmpolld.socket: Deactivated successfully.

 

[gfngfn256]

Most likely this is hardware related, as the PC believes the power/button has been pressed. You could try checking the physical button/s, & all cables that connect it to the motherboard. Static buildup could also cause this, (dry environment in server area?). Unstable power supply?

I also notice that it appears you have a nut-(server/client ?) connected. Not sure how you have set that up, but possibly that is triggering the shutdown? Unreliable power supply?