Proxmox shutting down after backup?

[thusband]

I recently had a problem with Proxmox not backing up after I updated to 7.4. There was an update and the backup problem was fixed but now Proxmox shuts down in the middle of the night after the backup. I'm not sure if the update changed something or where I should be looking to fix the problem. I'm including the syslog around the time I think the shutdown occurs. Any help greatly appreciated.

Mar 29 00:00:03 pve pvescheduler[193106]: <root@pam> starting task UPIDpve:0002F253:0058672A:64237173:vzdump::root@pam:
Mar 29 00:00:04 pve pvescheduler[193107]: INFO: starting new backup job: vzdump --all 1 --mode snapshot --node pve --notes-template '{{guestname}}' --mailnotification always --prune-backups 'keep-last=3' --compress zstd --quiet 1 --storage Storage --mailto xxxxx.xxx@xxxxxxx
Mar 29 00:00:04 pve pvescheduler[193107]: INFO: Starting Backup of VM 100 (qemu)
Mar 29 00:00:06 pve systemd[1]: Starting Rotate log files...
Mar 29 00:00:06 pve systemd[1]: Starting Daily man-db regeneration...
Mar 29 00:00:06 pve systemd[1]: Reloading PVE API Proxy Server.
Mar 29 00:00:06 pve systemd[1]: man-db.service: Succeeded.
Mar 29 00:00:06 pve systemd[1]: Finished Daily man-db regeneration.
Mar 29 00:00:07 pve pveproxy[193133]: send HUP to 961
Mar 29 00:00:07 pve pveproxy[961]: received signal HUP
Mar 29 00:00:07 pve pveproxy[961]: server closing
Mar 29 00:00:07 pve pveproxy[961]: server shutdown (restart)
Mar 29 00:00:07 pve systemd[1]: Reloaded PVE API Proxy Server.
Mar 29 00:00:07 pve systemd[1]: Reloading PVE SPICE Proxy Server.
Mar 29 00:00:07 pve spiceproxy[193140]: send HUP to 967
Mar 29 00:00:07 pve spiceproxy[967]: received signal HUP
Mar 29 00:00:07 pve spiceproxy[967]: server closing
Mar 29 00:00:07 pve spiceproxy[967]: server shutdown (restart)
Mar 29 00:00:07 pve systemd[1]: Reloaded PVE SPICE Proxy Server.
Mar 29 00:00:07 pve systemd[1]: Stopping Proxmox VE firewall logger...
Mar 29 00:00:07 pve pvefw-logger[600]: received terminate request (signal)
Mar 29 00:00:07 pve pvefw-logger[600]: stopping pvefw logger
Mar 29 00:00:08 pve systemd[1]: pvefw-logger.service: Succeeded.
Mar 29 00:00:08 pve systemd[1]: Stopped Proxmox VE firewall logger.
Mar 29 00:00:08 pve systemd[1]: pvefw-logger.service: Consumed 4.270s CPU time.
Mar 29 00:00:08 pve systemd[1]: Starting Proxmox VE firewall logger...
Mar 29 00:00:08 pve systemd[1]: Started Proxmox VE firewall logger.
Mar 29 00:00:08 pve pvefw-logger[193150]: starting pvefw logger
Mar 29 00:00:08 pve systemd[1]: logrotate.service: Succeeded.
Mar 29 00:00:08 pve systemd[1]: Finished Rotate log files.
Mar 29 00:00:08 pve spiceproxy[967]: restarting server
Mar 29 00:00:08 pve spiceproxy[967]: starting 1 worker(s)
Mar 29 00:00:08 pve spiceproxy[967]: worker 193154 started
Mar 29 00:00:08 pve pveproxy[961]: restarting server
Mar 29 00:00:08 pve pveproxy[961]: starting 3 worker(s)
Mar 29 00:00:08 pve pveproxy[961]: worker 193155 started
Mar 29 00:00:08 pve pveproxy[961]: worker 193156 started
Mar 29 00:00:08 pve pveproxy[961]: worker 193157 started
Mar 29 00:00:13 pve spiceproxy[968]: worker exit
Mar 29 00:00:13 pve spiceproxy[967]: worker 968 finished
Mar 29 00:00:13 pve pveproxy[143139]: worker exit
Mar 29 00:00:13 pve pveproxy[124887]: worker exit
Mar 29 00:00:13 pve pveproxy[126554]: worker exit
Mar 29 00:00:13 pve pveproxy[961]: worker 143139 finished
Mar 29 00:00:13 pve pveproxy[961]: worker 126554 finished
Mar 29 00:00:13 pve pveproxy[961]: worker 124887 finished
Mar 29 00:00:57 pve pvescheduler[193107]: INFO: Finished Backup of VM 100 (00:00:53)
Mar 29 00:00:57 pve pvescheduler[193107]: INFO: Starting Backup of VM 101 (lxc)
Mar 29 00:02:21 pve pvescheduler[193107]: INFO: Finished Backup of VM 101 (00:01:24)
Mar 29 00:02:21 pve pvescheduler[193107]: INFO: Starting Backup of VM 102 (lxc)
Mar 29 00:02:37 pve pvescheduler[193107]: INFO: Finished Backup of VM 102 (00:00:16)
Mar 29 00:02:37 pve pvescheduler[193107]: INFO: Backup job finished successfully
Mar 29 00:02:37 pve postfix/pickup[179568]: 4C64820A0D: uid=0 from=<root>
Mar 29 00:02:37 pve postfix/cleanup[193769]: 4C64820A0D: message-id=<20230328230237.4C64820A0D@pve.home>
Mar 29 00:02:37 pve postfix/qmgr[912]: 4C64820A0D: from=<root@pve.home>, size=16505, nrcpt=1 (queue active)
Mar 29 00:02:38 pve postfix/smtp[193771]: 4C64820A0D: to=<xxxxxx.xxxx@xxx.xxx>, relay=smtp.gmail.com[173.194.76.108]:587, delay=1.5, delays=0.02/0.04/0.31/1.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1680044558 e4-20020a5d4e84000000b002ceac2ccc4asm28708721wru.23 - gsmtp)
Mar 29 00:02:38 pve postfix/qmgr[912]: 4C64820A0D: removed
Mar 29 00:17:01 pve CRON[196862]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 29 00:17:01 pve CRON[196863]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 29 00:17:01 pve CRON[196862]: pam_unix(cron:session): session closed for user root
Mar 29 01:17:01 pve CRON[209265]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 29 01:17:01 pve CRON[209266]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 29 01:17:01 pve CRON[209265]: pam_unix(cron:session): session closed for user root
Mar 29 01:24:35 pve smartd[616]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 116 to 117
Mar 29 02:17:01 pve CRON[221702]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 29 02:17:01 pve CRON[221703]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 29 02:17:01 pve CRON[221702]: pam_unix(cron:session): session closed for user root
-- Reboot --

 

[leesteken]

Looks like the backup has nothing to do with it as it completed several hours earlier. There is also no indication that Proxmox shutdown gracefully and it appear to crash hard. Maybe a hardware failure, maybe an external factor (power interrupted?) or maybe an issue with the latest kernel? There appears to be no log about the crash itself. Did this happen more than once? If you can reproduce it, then it might help booting the previous kernel and seeing if that prevents the crash.

 

[thusband]

Looks like the backup has nothing to do with it as it completed several hours earlier. There is also no indication that Proxmox shutdown gracefully and it appear to crash hard. Maybe a hardware failure, maybe an external factor (power interrupted?) or maybe an issue with the latest kernel? There appears to be no log about the crash itself. Did this happen more than once? If you can reproduce it, then it might help booting the previous kernel and seeing if that prevents the crash.

Thanks for taking a look. Yes it's happened once before since the update to 7.4. I'm not sure how I'd reproduce the shutdown and I'll have to read up on booting to an earlier kernel because it sounds a little complicated. Perhaps just a complete re-install of Proxmox would be best since the only major thing I have running is Home Assistant.
Thanks again.

 

[leesteken]

Thanks for taking a look.

Unfortunately, there is nothing to look at.

I'll have to read up on booting to an earlier kernel because it sounds a little complicated.

You can start with (connecting a display and keyboard and) using the up arrow and enter key in the boot menu to manually select the previous kernel.

 

[thusband]

Unfortunately, there is nothing to look at.

You can start with (connecting a display and keyboard and) using the up arrow and enter key in the boot menu to manually select the previous kernel.

Right. That doesn't sound too tough. If it happens again I'll do it.
Again, thanks.