Problem adding another VPS on HyperVM

[Teks0427]

Is the host on xen or openvz virtualization?

Virtualization is OpenVZ. I tried vzctl stop and destroy...

# vzctl destroy 120
Container is currently running. Stop it first.

# vzctl stop 120
Stopping container ...
Unable to stop container: operation timed out

But they didn't work...

# vzlist 120
CTID NPROC STATUS IP_ADDR HOSTNAME
120 0 running 8x.xx.xx.x7 mydomain.com

---------- Post added at 02:31 AM ---------- Previous post was at 01:36 AM ----------

Try running the following commands on the main node:

cd /vz/private
mv 120 dead.120

This didn't work either... I'm now seriously considering backing everything up and just rebuilding the whole thing. The error is limiting the entire server to running just one VPS right now and its getting a bit irritating already.

Teks0427 Reviewed by Teks0427 on 25th Feb 2012. Problem adding another VPS on HyperVM I had 2 vps installed on my dedicated server, both running fine for around a month already until I decided to delete the second vps and tried to create a new one. As I was creating the new vps (add OpenVZ), I got an error saying... "A vps with the id 120 already exists on the system. This either means this was created outside of hyperVM or else it got orphaned because hyperVM was interrupted forcibly in the midst of a migration. You can either a) Login manually and delete the vps. or b) Rating: 5