Good day all - new to Proxmox, so please be patient with me.
I did see a search result of someone else having this issue, resolved by updating the kernel, but this is two years later and a fresh install - updated in April.
I received an alert from our backup application that the server (host) was shut down during a backup operation.
The logs I see appear to indicate it was restarted at midnight, but I cannot see what caused this. If it is automation/patch, etc, then I must have control over when this happens as we are operational at midnight (at times).
My system log entries that make me think it's restarting:
May 07 00:00:07 PVE-2025 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
May 07 00:00:07 PVE-2025 systemd[1]: Starting logrotate.service - Rotate log files...
May 07 00:00:07 PVE-2025 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
May 07 00:00:07 PVE-2025 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
May 07 00:00:07 PVE-2025 systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
May 07 00:00:07 PVE-2025 pveproxy[2050878]: send HUP to 1397
May 07 00:00:07 PVE-2025 pveproxy[1397]: received signal HUP
May 07 00:00:07 PVE-2025 pveproxy[1397]: server closing
May 07 00:00:07 PVE-2025 pveproxy[1397]: server shutdown (restart)
May 07 00:00:07 PVE-2025 systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
May 07 00:00:07 PVE-2025 systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
May 07 00:00:07 PVE-2025 spiceproxy[2050880]: send HUP to 1403
May 07 00:00:07 PVE-2025 spiceproxy[1403]: received signal HUP
May 07 00:00:07 PVE-2025 spiceproxy[1403]: server closing
May 07 00:00:07 PVE-2025 spiceproxy[1403]: server shutdown (restart)
May 07 00:00:07 PVE-2025 systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
May 07 00:00:07 PVE-2025 systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
May 07 00:00:07 PVE-2025 pvefw-logger[1725317]: received terminate request (signal)
May 07 00:00:07 PVE-2025 pvefw-logger[1725317]: stopping pvefw logger
May 07 00:00:08 PVE-2025 spiceproxy[1403]: restarting server
May 07 00:00:08 PVE-2025 spiceproxy[1403]: starting 1 worker(s)
May 07 00:00:08 PVE-2025 spiceproxy[1403]: worker 2050891 started
May 07 00:00:08 PVE-2025 systemd[1]: pvefw-logger.service: Deactivated successfully.
May 07 00:00:08 PVE-2025 systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
May 07 00:00:08 PVE-2025 systemd[1]: pvefw-logger.service: Consumed 4.871s CPU time.
May 07 00:00:08 PVE-2025 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
May 07 00:00:08 PVE-2025 pvefw-logger[2050894]: starting pvefw logger
May 07 00:00:08 PVE-2025 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
May 07 00:00:08 PVE-2025 systemd[1]: logrotate.service: Deactivated successfully.
May 07 00:00:08 PVE-2025 systemd[1]: Finished logrotate.service - Rotate log files.
May 07 00:00:08 PVE-2025 pveproxy[1397]: restarting server
May 07 00:00:08 PVE-2025 pveproxy[1397]: starting 3 worker(s)
May 07 00:00:08 PVE-2025 pveproxy[1397]: worker 2050899 started
May 07 00:00:08 PVE-2025 pveproxy[1397]: worker 2050900 started
May 07 00:00:08 PVE-2025 pveproxy[1397]: worker 2050901 started
May 07 00:00:13 PVE-2025 spiceproxy[1725314]: worker exit
May 07 00:00:13 PVE-2025 spiceproxy[1403]: worker 1725314 finished
May 07 00:00:13 PVE-2025 pveproxy[1954197]: worker exit
May 07 00:00:13 PVE-2025 pveproxy[1955297]: worker exit
May 07 00:00:13 PVE-2025 pveproxy[1949295]: worker exit
May 07 00:00:13 PVE-2025 pveproxy[1397]: worker 1954197 finished
May 07 00:00:13 PVE-2025 pveproxy[1397]: worker 1955297 finished
May 07 00:00:13 PVE-2025 pveproxy[1397]: worker 1949295 finished
I did see a search result of someone else having this issue, resolved by updating the kernel, but this is two years later and a fresh install - updated in April.
I received an alert from our backup application that the server (host) was shut down during a backup operation.
The logs I see appear to indicate it was restarted at midnight, but I cannot see what caused this. If it is automation/patch, etc, then I must have control over when this happens as we are operational at midnight (at times).
My system log entries that make me think it's restarting:
May 07 00:00:07 PVE-2025 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
May 07 00:00:07 PVE-2025 systemd[1]: Starting logrotate.service - Rotate log files...
May 07 00:00:07 PVE-2025 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
May 07 00:00:07 PVE-2025 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
May 07 00:00:07 PVE-2025 systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
May 07 00:00:07 PVE-2025 pveproxy[2050878]: send HUP to 1397
May 07 00:00:07 PVE-2025 pveproxy[1397]: received signal HUP
May 07 00:00:07 PVE-2025 pveproxy[1397]: server closing
May 07 00:00:07 PVE-2025 pveproxy[1397]: server shutdown (restart)
May 07 00:00:07 PVE-2025 systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
May 07 00:00:07 PVE-2025 systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
May 07 00:00:07 PVE-2025 spiceproxy[2050880]: send HUP to 1403
May 07 00:00:07 PVE-2025 spiceproxy[1403]: received signal HUP
May 07 00:00:07 PVE-2025 spiceproxy[1403]: server closing
May 07 00:00:07 PVE-2025 spiceproxy[1403]: server shutdown (restart)
May 07 00:00:07 PVE-2025 systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
May 07 00:00:07 PVE-2025 systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
May 07 00:00:07 PVE-2025 pvefw-logger[1725317]: received terminate request (signal)
May 07 00:00:07 PVE-2025 pvefw-logger[1725317]: stopping pvefw logger
May 07 00:00:08 PVE-2025 spiceproxy[1403]: restarting server
May 07 00:00:08 PVE-2025 spiceproxy[1403]: starting 1 worker(s)
May 07 00:00:08 PVE-2025 spiceproxy[1403]: worker 2050891 started
May 07 00:00:08 PVE-2025 systemd[1]: pvefw-logger.service: Deactivated successfully.
May 07 00:00:08 PVE-2025 systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
May 07 00:00:08 PVE-2025 systemd[1]: pvefw-logger.service: Consumed 4.871s CPU time.
May 07 00:00:08 PVE-2025 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
May 07 00:00:08 PVE-2025 pvefw-logger[2050894]: starting pvefw logger
May 07 00:00:08 PVE-2025 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
May 07 00:00:08 PVE-2025 systemd[1]: logrotate.service: Deactivated successfully.
May 07 00:00:08 PVE-2025 systemd[1]: Finished logrotate.service - Rotate log files.
May 07 00:00:08 PVE-2025 pveproxy[1397]: restarting server
May 07 00:00:08 PVE-2025 pveproxy[1397]: starting 3 worker(s)
May 07 00:00:08 PVE-2025 pveproxy[1397]: worker 2050899 started
May 07 00:00:08 PVE-2025 pveproxy[1397]: worker 2050900 started
May 07 00:00:08 PVE-2025 pveproxy[1397]: worker 2050901 started
May 07 00:00:13 PVE-2025 spiceproxy[1725314]: worker exit
May 07 00:00:13 PVE-2025 spiceproxy[1403]: worker 1725314 finished
May 07 00:00:13 PVE-2025 pveproxy[1954197]: worker exit
May 07 00:00:13 PVE-2025 pveproxy[1955297]: worker exit
May 07 00:00:13 PVE-2025 pveproxy[1949295]: worker exit
May 07 00:00:13 PVE-2025 pveproxy[1397]: worker 1954197 finished
May 07 00:00:13 PVE-2025 pveproxy[1397]: worker 1955297 finished
May 07 00:00:13 PVE-2025 pveproxy[1397]: worker 1949295 finished