OpenVZ Forum: Support » "VE already locked" after unsuccessful migration

Home » General » Support » "VE already locked" after unsuccessful migration

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

"VE already locked" after unsuccessful migration [message #11379]

Thu, 22 March 2007 10:44

ataraxis
Messages: 19
Registered: August 2006

Junior Member

Hi,

I wanted to move a VE from HN1 to HN2 because HN1 should get a kernel update.

Both HNs run 2.6.18-028test007 with a custom config.
vzctl version is 3.0.14-1dso31.2

Here is the output from the migration:
HN1:~# vzmigrate -v --online HN2 231
OPT:-v
OPT:--online
OPT:HN2
Starting online migration of VE 231 on HN2
OpenVZ is running...
Loading /etc/vz/vz.conf and /etc/vz/conf/231.conf files
Check IPs on destination node: <IP>
Preparing remote node
Copying config file
231.conf 100% 1150 1.1KB/s 00:00
Name jira assigned
Saved parameters for VE 231
Creating remote VE root dir
Creating remote VE private dir
Initializing remote quota
Quota init
Turning remote quota on
Syncing private
100%
Live migrating VE
Suspending VE
Setting up checkpoint...
suspend...
get context...
Checkpointing completed succesfully
Dumping VE
Setting up checkpoint...
join context..
dump...
Checkpointing completed succesfully
Copying dumpfile
dump.231 100% 493MB 32.9MB/s 00:15
Syncing private (2nd pass)
Syncing 2nd level quota
Dumping 2nd level quota
Copying 2nd level quota
quotadump.231 100% 21 0.0KB/s 00:00
Load 2nd level quota
Undumping VE
Restoring VE ...
Starting VE ...
vzquota : (warning) Quota is running for id 231 already
VE is mounted
undump...
Adding IP address(es): <IP>
Setting CPU units: 200033

----------------------------------------
Here i hit ctrl+c after a few minutes, because the application should not be offline that much and previous migrations have been faster although the VEs were bigger
----------------------------------------

Killed by signal 2.
Error: Failed to undump VE
Resuming...
arpsend: <IP> is detected on another computer : <MAC>
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e <IP> eth0 FAILED
vzquota : (error) Quota off syscall for id 231: Device or resource busy

vzquota : (warning) Quota is running for id 231

This is from vz.log on HN1:
2007-03-22T11:16:25+0100 vzctl : VE 231 : Setting up checkpoint...
2007-03-22T11:16:25+0100 vzctl : VE 231 : suspend...
2007-03-22T11:16:25+0100 vzctl : VE 231 : get context...
2007-03-22T11:16:25+0100 vzctl : VE 231 : Checkpointing completed succesfully
2007-03-22T11:16:25+0100 vzctl : VE 231 : Setting up checkpoint...
2007-03-22T11:16:25+0100 vzctl : VE 231 : join context..
2007-03-22T11:16:25+0100 vzctl : VE 231 : dump...
2007-03-22T11:16:29+0100 vzctl : VE 231 : Checkpointing completed succesfully
2007-03-22T11:20:53+0100 vzctl : VE 231 : Resuming...

This is from vz.log on HN2:
2007-03-22T11:07:15+0100 vzctl : VE 231 : Name jira assigned
2007-03-22T11:07:15+0100 vzctl : VE 231 : Saved parameters for VE 231
2007-03-22T11:14:27+0100 vzctl : VE 231 : Restoring VE ...
2007-03-22T11:14:27+0100 vzctl : VE 231 : Starting VE ...
2007-03-22T11:14:27+0100 vzctl : VE 231 : VE is mounted
2007-03-22T11:14:28+0100 vzctl : VE 231 : Adding IP address(es): 213.214.12.231
2007-03-22T11:14:28+0100 vzctl : VE 231 : Setting CPU units: 200033
2007-03-22T11:15:01+0100 vps-bandwidth : Statsfile for VPS 231 created.
2007-03-22T11:18:55+0100 vzctl : VE 231 : VE config file does not exist
2007-03-22T11:19:08+0100 vzctl : VE 231 : VE config file does not exist
2007-03-22T11:20:06+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:20:09+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:20:14+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:20:52+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:21:30+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:21:42+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:22:03+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:25:26+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:25:30+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:28:51+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:28:54+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:30:13+0100 vzctl : VE 231 : VE already locked
2007-03-22T11:31:09+0100 vzctl : VE 231 : VE start in progress...
2007-03-22T11:31:09+0100 vzctl : VE 231 : Restoring completed succesfully

Now I can't get rid of 231 on HN2
it always says "VE already locked"

Any Ideas? Thanks in advance.

Kai

Report message to a moderator

[Message index]

		"VE already locked" after unsuccessful migration By: ataraxis on Thu, 22 March 2007 10:44
		Re: "VE already locked" after unsuccessful migration By: Andrey Mirkin on Thu, 22 March 2007 14:22
		Re: "VE already locked" after unsuccessful migration By: ataraxis on Thu, 22 March 2007 15:44
		Re: "VE already locked" after unsuccessful migration By: Andrey Mirkin on Thu, 22 March 2007 16:38
		Re: "VE already locked" after unsuccessful migration By: ataraxis on Thu, 22 March 2007 16:49
		Re: "VE already locked" after unsuccessful migration By: ataraxis on Thu, 22 March 2007 17:13
		Re: "VE already locked" after unsuccessful migration By: Andrey Mirkin on Thu, 22 March 2007 17:41

Previous Topic:	SOLVED kernel error
Next Topic:	SOLVED Kernel Request -FC6 OpenVZ

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Apr 18 23:06:35 GMT 2026

Total time taken to generate the page: 0.23300 seconds