| VE already locked [message #28707] |
Wed, 26 March 2008 16:16  |
swapneel
Messages: 8
Registered: November 2007
|
Junior Member |
|
|
Hello Guys,
The hardware node was abruptly rebooted due to a problem in the power circuit.
We could see that a few of the VPS nodes were in 'stopped' state even though the veid.conf of the node had ONBOOT="yes"
Attempting to start or stop the node resulted in 'VE already locked'.
[root@server ~]# vzctl start 340
VE already locked
[root@server ~]# vzctl status 340
VEID 340 exist unmounted down
[root@server ~]# vzctl stop 340
VE already locked
Can anyone shed some light on how we can start these nodes ? Thanks
|
|
|
|
|
|
|
|
| Re: VE already locked [message #28716 is a reply to message #28707] |
Wed, 26 March 2008 19:04  |
TheWiseOne
Messages: 66
Registered: September 2005
Location: Pennsylvania
|
Member |
|
|
You should cat the lock file to see the process ID that has locked the CT. You can then kill the process ID listed. Just removing the lockfile and manipulating the CT with the process locking the CT still running is just asking for trouble.
Matt Ayres
TekTonic
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
