[3014]ERR: 24: Error in Perl code: unable to lock output file

[coffe]

Hi, Did a migrate , did get this error on new server. trying to move it back to old , to get it up and running.

Any solution to this problem ?


/C

 

[tom]

if a VM is in migration state, its locked. if you are sure that the lock is wrong (e.g. failed backup), you can manually unlock the VM:

see http://forum.proxmox.com/threads/3862-Aborted-migration

if this is not the case pls give more details what you do, how to reproduce the issue.

 

[coffe]

Hi,
Migration went well . and machine where running on new host. but i could not connect to it. or shut it down or anything.

/c

 

[tom]

in your first post you write that had to move it back to get it running.

so pls describe in detail what you are doing, also provide details about your setup and where you get the error.

 

[coffe]

Hi,

After migration. i did see it where running on new server. could not connect to it , and when trying to start console i just got a blackscreen.
Trying to restart it from WEBgui just resultet in the error thats it this threds subject.


What i did to do. as it where one of our ldap servers . i did kill pid. copy config. , and then a qm unlock on old server.
/c

 

[tom]

again, I need details.

what do you migrate, how, post migration log? Proxmox VE version (pveversion -v), etc.
if you do not report this in detail it is impossible to see any issue.

 

[coffe]

migrationlog :
/usr/sbin/qmigrate --online 192.168.17.31 128
May 21 08:58:57 starting migration of VM 128 to host '192.168.17.31'
May 21 08:58:57 copying disk images
May 21 08:58:57 starting VM on remote host '192.168.17.31'
May 21 08:58:58 starting migration tunnel
May 21 08:58:58 starting online/live migration
May 21 08:59:14 migration status: completed
May 21 08:59:14 migration speed: 16.00 MB/s
May 21 08:59:16 migration finished successfuly (duration 00:00:20)
VM 128 migration done


pveversion -v

From server:
pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1


To server:
pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-4
pve-kernel-2.6.32-1-pve: 2.6.32-4
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3

 

[tom]

any special reason having different kernels?

 

[coffe]

No, dont know why it where not updated the day before. so now i have updated the second server and rebooted it.