Backup time out but was still completed.

[Erick3k]

Hello

On Proxmox VE provides an error: unexpected status / ERROR: can't acquire lock '/var/run/vzdump.lock' - got timeout

However, operantly the backup was still completed on Proxmox Backup end.

It is a little concerning because, you expect the got timeout to stop the backup, yet it was done and no record of it on Proxmox VE.

 

[dcsapak]

can you post the complete failed task log?

 

[Erick3k]

()

Task viewer: VM/CT 101 - Backup

OutputStatus


INFO: trying to get global lock - waiting...
ERROR: can't acquire lock '/var/run/vzdump.lock' - got timeout

 

[dcsapak]

but it seems that's not the same task log as in your screenshot above with the 'unexpected status' error?

 

[Erick3k]

but it seems that's not the same task log as in your screenshot above with the 'unexpected status' error?

Can you explain? that is indeed the same task log on the proxmox VE on the screenshot, the second screenshot is proxmox backup. Are you asking for a different task log? i guarantee you, that is the correct task log for 1 VM all other 3 say the exact same

 

[Erick3k]

Maybe this helps, otherwise sorry but i'm not sure what you are referring to then.

Regards

 

[fiona]

Hi,
the timeout error likely means that there was still another backup running at that time. By default, each vzdump invocation waits 180 minutes for the lock. This can be controlled via the --lockwait CLI option. You can also change your schedules, so there is enough time in between or maybe you can group some jobs together.

 

[Erick3k]

Hi,
the timeout error likely means that there was still another backup running at that time. By default, each vzdump invocation waits 180 minutes for the lock. This can be controlled via the --lockwait CLI option. You can also change your schedules, so there is enough time in between or maybe you can group some jobs together.

Thank you, however all i'm reporting on is that there was an error of timeout yet backup completed with no way of knowing that on the proxmox backend unless you actually take a look at the backup storage. Upon timeout i would guess that i would expect the backup to stop but seems like is not the case. I have no issue or anything to fix on my end. Just pointing out if is a bug or could cause backup notifications to not work.

Anyway, appreciate the tips.