Migration fails with proxmox HA cluster

AhmedF

Renowned Member
Dec 26, 2012
26
1
68
Hi,

I'm trying to migrate a container between nodes in HA cluster but am getting the following error , can you please advise ?

Code:
task started by HA resource agent
Feb 17 08:11:05 starting migration of CT 100 to node 'proxmoxZ' (192.168.x.x)
Feb 17 08:11:05 container is running - using online migration
Feb 17 08:11:05 container data is on shared storage 'NFSHDD'
Feb 17 08:11:05 start live migration - suspending container
Feb 17 08:11:05 dump container state
Feb 17 08:11:07 dump 2nd level quota
Feb 17 08:11:08 # vzctl --skiplock umount 100
Feb 17 08:11:08 ERROR: Failed to umount container: Can't umount /var/lib/vz/root/100: Device or resource busy
Feb 17 08:11:08 aborting phase 1 - cleanup resources
Feb 17 08:11:08 start final cleanup
Feb  17 08:11:08 ERROR: migration aborted (duration 00:00:04): Failed to  umount container: Can't umount /var/lib/vz/root/100: Device or resource  busy
TASK ERROR: migration aborted
 
"Device or resource busy" in openvz usually means that theres an open system shell that has its current working directory inside the container area. cd out of the containers folder and you should be good to go
 
Thanks for your answer but no one is even logged in this container from the main node or from outside and my only opened shell is in /root for the main node so no one is even opening this folder

/var/lib/vz/root/100
 
lsof should be able to tell if who/what if anything is using that directory:

apt-get install lsof
lsof /var/lib/vz/root/100

now unfortunately this list will also show pretty much all the processes running inside the container, so you have to look closely which process is not a container process

if this test comes up "clean" (= dont see anything that shouldnt be there), Im out of ideas, sorry.
 
Thanks but I don't think this is related to open files as it worked once without any changes from another node but not getting the same error again from both nodes and now getting this error

Code:
Feb 17 08:57:52 proxmoxc pvedaemon[2430]: <root@pam> starting task UPID:proxmoxc:000011DD:00002481:5120EFF0:hastart:101:root@pam:
Feb 17 08:57:54 proxmoxc rgmanager[1930]: #43: Service pvevm:101 has failed; can not start.
Feb 17 08:57:54 proxmoxc rgmanager[1930]: #13: Service pvevm:101 failed to stop cleanly
Feb 17 08:57:54 proxmoxc pvedaemon[4573]: command 'clusvcadm -e pvevm:101 -m proxmoxc' failed: exit code 254
Feb 17 08:57:54 proxmoxc pvedaemon[2430]: <root@pam> end task UPID:proxmoxc:000011DD:00002481:5120EFF0:hastart:101:root@pam: command 'clusvcadm -e pvevm:101 -m proxmoxc' failed: exit code 254
 
Here is the error !!

root@proxmoxa:~# vzctl umount 100
Can't umount /var/lib/vz/root/100: Device or resource busy
root@proxmoxa:~# vzctl umount 100
Can't umount /var/lib/vz/root/100: Device or resource busy
root@proxmoxa:~# vzctl umount 100
Can't umount /var/lib/vz/root/100: Device or resource busy
root@proxmoxa:~# lsof | grep "/var/lib/vz/root/100"
root@proxmoxa:~# vzctl umount 100
Container is unmounted
root@proxmoxa:~#
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!