[SOLVED] Backups failing after update to 7.1

[cdsJerry]

I updated to version 7.1-8 but have been having problems with backups ever since. At first the backups were all failing reporting they were unable to get a lock. In an effort to resolve the problem I deleted all my backup schedules and have recreated new ones so I could make _sure_ there was no overlap in times but it's still failing. I have a job from Jan 24th that's still "running" and I've been unable to stop it. Other backups fail, probably as a result.

The backup from Jan 24th is currently showing a status of "INFO: 1% (7.1 GiB of 700.0 GiB) in 4m 12s, read: 25.8 MiB/s, write: 25.1 MiB/s" which it's been showing for a long time. I've tried clicking the Stop button on the Task viewer but nothing happens.

As one might expect, all backup jobs since then have an error

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

I have tried the "qm unlock 105" command which returns no error, but doesn't stop the backup or unlock the VM either.

root@pve:~# ps auxww|grep vzdump
root 730596 0.0 0.0 363836 41056 ? Ss 07:32 0:00 task UPIDve :000B25E4:08AB57EA:61F9284F:vzdump:105:root@pam:
root 745904 0.0 0.0 6180 724 pts/0 S+ 08:53 0:00 grep vzdump
root 2870207 0.0 0.0 349604 43712 ? Ds Jan24 2:28 task UPIDve :002BCBBF:04C0A497:61EF2165:vzdump::root@pam:

Short of rebooting the entire system, how do I get this stuck backup to stop so other backups can proceed?

 

[oguz]

hi,

Short of rebooting the entire system, how do I get this stuck backup to stop so other backups can proceed?

have you tried that after the upgrades were done?

if the issue keeps happening after a reboot, please post:

* pveversion -v
* the full output from the task log of the backup job (try with a new one)
* journalctl output at the time of backup

 

[cdsJerry]

hi,


have you tried that after the upgrades were done?

if the issue keeps happening after a reboot, please post:

* pveversion -v
* the full output from the task log of the backup job (try with a new one)
* journalctl output at the time of backup

Of course I had rebooted after the upgrade. I think I did it again when it was hanging all the backups but I can't remember for sure if I did it, or just thought about doing it. I've rebooted it just now and manually started one of the backups. It seems to have started OK. I'll see how it's doing in an hour or so. The NIC on this Dell never passes traffic as fast as I think it should (130 MB/s).