Problem adding another VPS on HyperVM

[Teks0427]

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) Use our import facility to import this vps into hyperVM. Sorry for the inconvenience."

The import facility couldn't find anything to import and I don't know what they mean by "Login manually and delete the vps" or if that's even possible. Where am I supposed to "login manually"? What am I supposed to delete? The LxCenter forum wasn't much help either.

There are still free resources remaining on the server, since I was planning to create the new one where the old one was.

This is the first time I've come across something like this. I've created at least 25+ vps on various servers and have always used HyperVM. I can't rebuild the entire server as the other vps is being used by several other people at present. I just need to be able to create another vps.

The server's OS is CentOS 5.7 64bit.

Thank you in advance to anyone who can help me fix this problem.

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

[masterb56]

Is the host on xen or openvz virtualization?

[DaringHost]

Try running the following commands on the main node:

cd /vz/private
mv 120 dead.120

[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.

[masterb56]

How about this:

vzctl set 120 --onboot no --save

And then restart the server and delete the container.

[Teks0427]

This is weird... I tried:

[root@bxxxxxx ~]# vzctl set 120 --disabled yes --save
CT configuration saved to /etc/vz/conf/120.conf

then rebooted the entire server, and ran:

[root@bxxxxxx ~]# vzctl destroy 120
CTID NPROC STATUS IP_ADDR HOSTNAME
[root@bxxxxxx ~]#

Seems to work up to this point...

But when I "Add OpenVZ" again on HyperVM, the error comes back and the cycle repeats itself.

[masterb56]

Well the destroy command should be able to give you a confirmation message or something, that should be a sign that it really didn't work. Have you tried entering the vps?

[Sonic]

why don't use solusvm