You usually have to restart the "prl-disp" service when you have this
kind of problems and/or to "prlctl unregister" and/or "vzctl unregister".
On 7/6/20 5:07 PM, Jehan Procaccia IMT wrote:
Hello
because I have a fail CT on a hardware node , cf
https://lists.openvz.org/pipermail/users/2020-July/007928.html
I moved manually the CT files (hdds, conf, etc ...) to another
hardware node (HW) that doesn't seem to have the pb yet ( not
updateded to OpenVZ release 7.0.14 (136))
I did a rsync of /vz/private/CTID from HWsrc to HWdest and created in
/etc/vz/conf on HWdest the associated link to the conf file
ln -s /vz/private/144dc737-b4e3-4c03-852c-25a6df06cee4/ve.conf
144dc737-b4e3-4c03-852c-25a6df06cee4.conf
but still , a prctl list --all doesn't show that newly "moved" CT .
How can I tell HWdest that there is a new CT on it ? I tried a
register command
# prlctl register /vz/private/144dc737-b4e3-4c03-852c-25a6df06cee4
Register the virtual environment...
Failed to register the virtual environment:
PRL_ERR_VZCTL_OPERATION_FAILED (Details: Container is already
registered with id 144dc737-b4e3-4c03-852c-25a6df06cee4
Container registration failed: Container is already registered with id
144dc737-b4e3-4c03-852c-25a6df06cee4
)
but it is already registered .
is there a way to "reload/refresh" something to enable the run of that
moved CT ?
Thanks .
_______________________________________________
Users mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/users
