I noticed that my Proxmox host was not responding to any pings along with my containers. My hardware still was on though, I did a force restart and checked my Proxmox logs right before it crashed and found this:
I'm not sure as to what caused this 'reboot' because it never booted back into Proxmox until I force restarted the system, If it helps I run a Ubuntu 24.04 running in a privileged container (used the official 22.04 template and upgraded to 24.04) and a homeassistant virtual machine. Any help would be appreciated.
Code:
Sep 23 08:17:01 firebolt CRON[3685457]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 23 08:17:01 firebolt CRON[3685456]: pam_unix(cron:session): session closed for user root
Sep 23 09:12:28 firebolt systemd[1]: Starting apt-daily.service - Daily apt download activities...
Sep 23 09:12:29 firebolt systemd[1]: apt-daily.service: Deactivated successfully.
Sep 23 09:12:29 firebolt systemd[1]: Finished apt-daily.service - Daily apt download activities.
Sep 23 09:17:01 firebolt CRON[3745720]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Sep 23 09:17:01 firebolt CRON[3745721]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 23 09:17:01 firebolt CRON[3745720]: pam_unix(cron:session): session closed for user root
Sep 23 10:17:01 firebolt CRON[3805843]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Sep 23 10:17:01 firebolt CRON[3805844]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 23 10:17:01 firebolt CRON[3805843]: pam_unix(cron:session): session closed for user root
-- Reboot --I'm not sure as to what caused this 'reboot' because it never booted back into Proxmox until I force restarted the system, If it helps I run a Ubuntu 24.04 running in a privileged container (used the official 22.04 template and upgraded to 24.04) and a homeassistant virtual machine. Any help would be appreciated.