container locked

[typo3usa]

/usr/sbin/vzctl start 6002
Container already locked
VM 6002 start failed -

Any ideas?

have tried rebooting host node - no go

 

[mastens]

Hi,

Take a look in /var/lib/vz/lock , and delete the lock file that belongs to the VM.

Marius

 

[typo3usa]

removed / rebooted - and still no go
this is a killer sadly

tons of important things on this vps :-(

 

[mastens]

Hmm, i'm guessing the HN tryes to start the VM during boot ?
If it does, something in this vm is very bugged probably, try remove the lock file without reboot after, and tail -f /var/log/vzctl.log and start the VM at the same time.... see what the log file says.

 

[typo3usa]

looks like the same issue again

hmmm

2009-08-20T13:39:52-0400 vzctl : CT 6002 : Starting container ...
2009-08-20T13:39:52-0400 vzctl : CT 6002 : vzquota on failed [7]

trying to figure it out yet again

deleted the lock - then restarted - error log shows vzquota issues

 

[john.gil]

I do not know about OpenVZ implemented by Proxmox but if that was a pure OpenVZ node I would try:

vzctl stop 6002
vzquota drop 6002
vzctl start 6002

Try this only at your own risk of after an expert here confirms it, actually on an OpenVZ node the above would purge and recalculate the quota.