[SOLVED] Creating a CT error: "Could not reserve ID XXXX, already taken"

[Dolomike]

I recently attempted to join another Proxmox host into a cluster but ran into errors and wasn't able to complete the process so I left it for now but now when I attempt to create a container, I get the following error:

TASK ERROR: Could not reserve ID XXXXX, already taken

I've attempted a a number of available ID's but I get the same result.

So what's going on that's preventing container creation? Is there something with the failed cluster process that caused this?

Running Proxmox 4.4-1/eb2d6f1e

 

[wolfgang]

Hi,
first I would upgrade all nodes to current version.
Then recheck.

 

[Dolomike]

Hi,

Yeah, I tried that yesterday as well but still the same result.

It works fine on the "slave" node but not on the "master" node that I started the cluster process on. I'll see if I can get the cluster operational and report back.

 

[Dolomike]

The /etc/pve/corosync.conf file was un-writable so the cluster was "invalid" and for whatever reason this prevents new CT's from being created.

I stopped the corosync service and switched to local only mode:

service corosync stop
pmxcfs -l

I was then able to delete /etc/pve/corosync.conf, rebooted and it now seems to be functioning normally.

Hopefully this helps someone else in the future!

 

[fernan.mont]

Hi,
I'm getting the same error but I didn't attempted to join another proxmox host. The /etc/pve/corosync.conf doesn't exist so, how do you get to the point that was that file the problem? Maybe there is another file un-writable...

I'm running the same version: 4.4-1/eb2d6f1e

I'm really new in proxmox and linux servers and I'm a bit lost.

Thanks in advanced!

 

[Dolomike]

The only thing I can think of is that there is a file that Proxmox can't write to or that you actually have that id already taken. Check your vm config files and make sure that ID doesn't exist and that the correct permissions are set on the required config files.