Scheduled backup fails, manual works fine...???

[LooneyTunes]

Hi,

I recently posted about a similar issue here, and thought it was resolved and the reason found, but not so sure now. This morning I found that yet another scheduled backup had failed, same machine, an almost identical error;

INFO: transferred 32.00 GiB in 7317 seconds (4.5 MiB/s)
zstd: /*stdout*\: Bad file descriptor
Warning: unable to close filehandle GEN987 properly: Host is down at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 770.
ERROR: Backup of VM 101 failed - zstd --rsyncable --threads=1 failed - wrong exit status 1
INFO: Failed at 2022-08-13 03:36:13
INFO: Starting Backup of VM 102 (qemu)

Similarly as before. it fails on line 770 in 'QemuServer.pm', not being able to close a file handle, but this time the error above that is different. I have checked my NAS, and it works fine for all intents and purposes, nothing in the logs.

This failing backup is in the middle of others that has worked just fine, so very strange. Can this be due to some issue with the VM itself? Can it be tested/recreated/verified in some way? But at the same time, if it should turn out to be the VM, why would a manual trigger of the same backup-job work?

Edit: I just started the same backup-job (above), and now the first machine hangs it at 50% done. It timed out after some 20 minutes with

Error: unexpected status

Thanks

 

[Neobin]

Also, as a result of this, the machine is still marked as "Status: running, Config locked (backup)". How could I clear that and have it restarted again please? I believe I have seen a command for that somewhere, have searched but did not find it.

qm unlock <VMID>

Only do that if you are sure the action which set the lock is no longer running.

https://pve.proxmox.com/pve-docs/qm.1.html

 

[LooneyTunes]

qm unlock <VMID>

https://pve.proxmox.com/pve-docs/qm.1.html

Thanks! I actually found it, had documented it in a non-usual place. Thanks for the link, will read that too