proxmox backup won't stop

[offerlam]

hi all

here is my pvevserion -v output

root@proxmox00:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@proxmox00:~#

I have a 3 node setup.. for some reason my backup won't stop. I have tried to stop it though the GUI/Web but it still keeps going..

also it seems it stop taking backups so it seems the system is waiting for this backup to stop before starting a new.

how to manually kill it.

 

[t.lamprecht]

Hello!
Use

vzdump -stop

on the machine where the Backup is running.

 

[wolfgang]

Hi,
use on the command line
ps -aux | grep vzdump

kill -9 processId

then
qm unlock <vmid>
vmid of the hanging backup

 

[offerlam]

Hi t.lamprecht

thanks for the quick answer..

would i need to do something after to make sure backup starts again at 20 this evening? or?

also would this command affect production of the VMs?

Thanks

Casper

 

[t.lamprecht]

No should affect anything, stops only running backup jobs.

When it fails (could be as it isn't responding on the GUI command anymore) use wolfgangs method, which works for sure.

 

[offerlam]

Hi and sorry for the long response...

im not really sure what process im suppose to kill?

root@proxmox00:~# ps -aux | grep vzdump
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
root 678932 0.0 0.0 7788 936 pts/0 S+ 16:58 0:00 grep vzdump
root 757933 0.0 0.0 4136 536 ? Ss Aug11 0:00 /bin/sh -c vzdump 104 105 107 109 110 117 116 122 111 103 --quiet 1 --mode snapshot --mailto casper@dingit.dk --compress lzo --storage Backup01
root 757934 0.0 0.1 201560 39056 ? S Aug11 2:30 /usr/bin/perl -w -T /usr/bin/vzdump 104 105 107 109 110 117 116 122 111 103 --quiet 1 --mode snapshot --mailto casper@dingit.dk --compress lzo --storage Backup01
root 757945 0.0 0.1 200444 36020 ? Ds Aug11 2:19 task UPIDroxmox00:000B90B9:94BDB694:55CA4632:vzdump::root@pam:
root@proxmox00:~#

im not wich if not all?

 

[t.lamprecht]

These two should suffice: 757933 and 757934.

 

[offerlam]

I killed the processes on the two of the three nodes which had backups running and stuck..

they are now not showing in the AUX list - but the web gui still shows them running.. should i just wait or?

 

[t.lamprecht]

There is also a task process in your output, the one with the UUID, kill that too, this one should be responsible for the GUI.

 

[offerlam]

when i do the kill -9 processID it doesn't kill the process?

root@proxmox00:~# ps -aux | grep vzdump
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
root 227059 0.0 0.0 7788 928 pts/0 S+ 10:35 0:00 grep vzdump
root 757945 0.0 0.1 200444 36020 ? Ds Aug11 2:19 task UPIDroxmox00:000B90B9:94BDB694:55CA4632:vzdump::root@pam:
root@proxmox00:~# kill -9 757945
root@proxmox00:~# ps -aux | grep vzdump
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
root 227163 0.0 0.0 7788 924 pts/0 S+ 10:36 0:00 grep vzdump
root 757945 0.0 0.1 200444 36020 ? Ds Aug11 2:19 task UPIDroxmox00:000B90B9:94BDB694:55CA4632:vzdump::root@pam:
root@proxmox00:~# sudo kill -9 757945
-bash: sudo: command not found
root@proxmox00:~# ps -aux | grep vzdump

how should i proceed? also gui still shows backup as running and no backups are being done

thanks for all your help so fare

 

[dietmar]

I guess there is a non working NFS share involved? You can either try to get the NFS server online again, or reboot the node.
To avoid such things, you can mount backup shares with option 'soft', see

# man nfs

for details.

 

[offerlam]

hmm you are right.. the NAS is unresponsive.. !!

thanks!

should the option soft be set on proxmox node or NAS or both?

 

[dietmar]

should the option soft be set on proxmox node or NAS or both?

That is a client option, so you need to set that on the proxmox node.

 

[jostein]

okey. this is a workround this

for example:
umount -f /mnt/pve/<NAME OF MOUNT> and then kill it in consol by kill -9 or in gui. takes 1min but easy to fix.

 

[thiagotgc]

I had the same problem, but I couldn't unmount the NFS drive or stop the backup.

However, when restarting the services, PVE released the locked backup, and then I was able to successfully stop it!

killall -9 corosync
systemctl restart pve-cluster
systemctl restart pvedaemon
systemctl restart pvestatd
systemctl restart pveproxy

 

[Mattthias WW]

I was able to unlock the vm with: "vm unlock <vmid>"

 

[Cadsfg786]

Another solution is just update (was kernel update) Proxmox - in 7.4.-4 works almost perfectly (still backup Job but VMs works).

 

[aoiblue775]

I had the same problem, but I couldn't unmount the NFS drive or stop the backup.

However, when restarting the services, PVE released the locked backup, and then I was able to successfully stop it!

killall -9 corosync
systemctl restart pve-cluster
systemctl restart pvedaemon
systemctl restart pvestatd
systemctl restart pveproxy

This worked for me, thanks!