Hi all,
I updated my proxmox intallations from 2.3 to version 3.4 on two servers.
One with subscription-key, one without.
On the server with subscription and enterprise repo, I get following error when I try to start or dump a container:
I already deleted the /var/lib/vz/lock/ VCID.lck, but still not able to start the container.
The container is located on a separate storage with NFS, storage is mounted and I can access it from therminal within proxmox.
On the testingserver (no-subscription repo) all containers work fine.
Any idea??
I updated my proxmox intallations from 2.3 to version 3.4 on two servers.
One with subscription-key, one without.
On the server with subscription and enterprise repo, I get following error when I try to start or dump a container:
Code:
[COLOR=#000000][FONT=tahoma]Container already locked[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: command 'vzctl start 101' failed: exit code 9
or
[/FONT][/COLOR][COLOR=#000000][FONT=tahoma]Container already locked[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: command 'vzctl destroy 101' failed: exit code 9[/FONT][/COLOR][COLOR=#000000][FONT=tahoma]
[/FONT][/COLOR]I already deleted the /var/lib/vz/lock/ VCID.lck, but still not able to start the container.
The container is located on a separate storage with NFS, storage is mounted and I can access it from therminal within proxmox.
On the testingserver (no-subscription repo) all containers work fine.
Any idea??
Last edited: