Backups fail : ERROR: can't aquire lock '/var/run/vzdump.lock'

[dgallig]

Hello ,
backups are not working anymore ( storage are not full! )
I 've got this error:
INFO: trying to get global lock - waiting...
ERROR: can't aquire lock '/var/run/vzdump.lock' - got timeout

Any idea?


pveversion -v
proxmox-ve-2.6.32: 3.4-171 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-11 (running version: 3.4-11/6502936f)
pve-kernel-2.6.32-44-pve: 2.6.32-171
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-19
qemu-server: 3.4-6
pve-firmware: 1.1-5
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-34
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-20
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[dietmar]

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

Seems another vzdump process is still running?

 

[dgallig]

Hello, thanks for your reply dietmar.
There was no other process running, anyway there was a vzdump lock around. I removed it , tried again and had an "error 25".
I manually unlocked every vm, then tried again. Still some errors , but I think the problem is with the dump dir , a filesystem mounted via cifs... I'm opening a tiket with the provider... Many thanks

 

[VolkerK]

Did you find out, what was wrong?
I get the same error too for some days now. Same setup: backup goes to cifs share.

 

[vmanyushin]

for guys who search this error

check if no exists vzdump process running, then go to /var/run/, check if there vzdump.pid + vzdump.lock files exists if it there, delete it and try to run backup again.

 

[netdesignate]

I had to do the following in the end:
Plus I cleared the lock & pid files etc, and then I could run a new backup successfully.
This was run on:

root@pve:/USB-Backup/dump# pveversion​

pve-manager/5.2-7/8d88e66a (running kernel: 4.15.18-2-pve)
root@pve:/USB-Backup/dump# date
Sat Feb 16 11:28:47 EST 2019

root@pve:/etc/pve/lxc# lvdisplay
<SNIP>
--- Logical volume ---
LV Path /dev/pve/snap_vm-100-disk-1_vzdump
LV Name snap_vm-100-disk-1_vzdump

root@pve:~# cd /var/run
root@pve:/var/run# ls -al vzd*
-rw-r--r-- 1 root root 0 Feb 15 17:48 vzdump.lock
-rw-r--r-- 1 root root 53 Feb 16 01:15 vzdump.pid



root@pve:/etc/pve/lxc# lvremove /dev/pve/snap_vm-100-disk-1_vzdump
Do you really want to remove and DISCARD active logical volume pve/snap_vm-100-disk-1_vzdump? [y/n]: y
Logical volume "snap_vm-100-disk-1_vzdump" successfully removed

root@pve:/etc/pve/lxc# vzdump 100 --mode snapshot --remove 0 --storage USBKEY-BACKUP --compress lzo --node pve
INFO: starting new backup job: vzdump 100 --mode snapshot --storage USBKEY-BACKUP --remove 0 --compress lzo --node pve
INFO: Starting Backup of VM 100 (lxc)

<SNIP>

INFO: Finished Backup of VM 100 (00:56:58)
INFO: Backup job finished successfully
​

 

[xigloo]

for guys who search this error

check if no exists vzdump process running, then go to /var/run/, check if there vzdump.pid + vzdump.lock files exists if it there, delete it and try to run backup again.

hi, I have a question on your post: how can I check that the vzdump process is running?