Hey there,
we are not able to zero-downtime-migrate a CT,
the target HN brings the following error description:
root@ovz-b:~# vzctl restore 2000
Restoring container ...
Starting container ...
Container is mounted
undump...
Setting CPU units: 1000
Configure veth devices: veth2000.0
Error: undump failed: No such file or directory
Restoring failed:
Error: can't open file /var/run/apache2/.nfs00000000005430960000004e
Error: rst_file: -2 46240
Error: rst_files: -2
Error: make_baby: -2
Error: rst_clone_children
Container start failed
Stopping container ...
Container was stopped
Container is unmounted
The file is created everytime Apache2 starts on the CT and is removed as soon as Apache2 stops.
Also, we can't just "delete" the file because Apache2 keeps filesystem locks on it:
root@ct2000:/# lsof | grep .nfs
apache2 456 root 9w REG 0,27 0 5517462 /var/run/apache2/.nfs000000000054309600000073
apache2 472 www-data 9w REG 0,27 0 5517462 /var/run/apache2/.nfs000000000054309600000073
apache2 473 www-data 9w REG 0,27 0 5517462 /var/run/apache2/.nfs000000000054309600000073
apache2 474 www-data 9w REG 0,27 0 5517462 /var/run/apache2/.nfs000000000054309600000073
apache2 475 www-data 9w REG 0,27 0 5517462 /var/run/apache2/.nfs000000000054309600000073
apache2 476 www-data 9w REG 0,27 0 5517462 /var/run/apache2/.nfs000000000054309600000073
It seems that this file prevents us from using zero-downtime migration completely, is there any way to debug this?
OpenVZ Forum
Members
Search
Help
Register
Login
Home
