Recovering Orpaned CT

[ehplus]

Ok, I screwed up. I was personalizing the host system after installing a CT and changed the hostname file. The CT I set up is now orphaned to a node that doesn't exist. I mean, the files are fine and I am able to access it as a container, but it's messed up. I've created a second CT and changed the 101.conf file in /etc/pve/node/dedi1/openvz/ to refer to 100's information which is located in /etc/pve/node/ns40068/openvz/100.conf.

101 is meaningless, and currently I'm accessing 100's container by starting and stopping 101. It's messed up. Modifying 100.conf in the second directory keeps telling me it fails for some reason or another "Error 4" according to WinSCP.

Any idea how I can get the 100.conf file fixed and just delete 101?

Thanks,

Tyler

 

[dietmar]

Just mode the configuration file to the correct node:

# mv /etc/pve/node/<OLDNODE>/openvz/<VMID>.conf /etc/pve/node/<HOSTNAME>/openvz/

 

[ehplus]

Right ... Well ... I feel a little sheepish ... I tried everything EXCEPT the obvious mv command. Bah.

Thanks Dietmar, worked perfectly and everything is cleared up.

Cheers,

Tyler