OpenVZ Forum


Home » General » Support » "VE already locked" after unsuccessful migration
Re: "VE already locked" after unsuccessful migration [message #11397 is a reply to message #11388] Thu, 22 March 2007 15:44 Go to previous messageGo to previous message
ataraxis is currently offline  ataraxis
Messages: 19
Registered: August 2006
Junior Member

HN2:~# cat /proc/vz/veinfo
245 0 137 x.y.z.245
232 0 154 x.y.z.232
233 0 40 x.y.z.233
239 0 177 x.y.z.239
247 0 106 x.y.z.247
248 0 201 x.y.z.248
246 0 125 x.y.z.246
0 0 136

HN2:~# cat /proc/vz/veip
Version: 2.5
x.y.z.232 0
x.y.z.233 0
x.y.z.239 0
x.y.z.245 0
x.y.z.246 0
x.y.z.247 0
x.y.z.248 0

HN2:~# grep -i lock /etc/vz/vz.conf
LOCKDIR=/var/lib/vz/lock
HN2:~# ls /var/lib/vz/lock/ -l
insgesamt 0


After lunch I was suddenly able to delete the VE.
I tried to move the VEs then to a third server, it worked flawless there.

Here are infos about the third one:
HN3:~# cat /proc/vz/veinfo
241 2 168 x.y.z.241
231 2 89 x.y.z.231
240 0 178 x.y.z.240
104 0 241 x.y.z.237
0 0 125

HN3:~# cat /proc/vz/veip
Version: 2.5
x.y.z.231 0
x.y.z.237 0
x.y.z.240 0
x.y.z.241 0


I then updated HN1 to 2.6.18-028stab021 and then moving a VE to HN2 worked flawless.

Report message to a moderator

[Message index]
 
Read Message icon5.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: *SOLVED* kernel error
Next Topic: *SOLVED* Kernel Request -FC6 OpenVZ
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 24 04:38:20 GMT 2026

Total time taken to generate the page: 0.40531 seconds
Powered by FUDforum Powered by Virtuozzo Containers