Search

Language:  
Search for:

Available article translations:

[FIX] VE migration fails with 183 error code

Symptoms

VE migration of a specific VE fails with the following error:

C:\Documents and Settings\Administrator>vzmigrate -A 192.168.45.81  -P password 9991
connection adjust...
migrate 9991->9991
migration started
connect
get SSH keys
set SSH keys
prepare migration
close connection
Operation migrate with the VPS(s) VEID9991 Migration of the following VEs with V
EIDs 9991 to 192.168.45.81 is started.
Processing stage CheckParameters
Operation migrate with the VPS(s) VEID9991 Migration of the following VEs with V
EIDs 9991 to 192.168.45.81 is finished with errors: #3404 V2V migration failed : SW
AHaulControlOperator with id 'vzmigrate_v2v_serializer' stage 'CheckParameters'
failed : Virtuozzo API function call 'VZVolumeMount' failed err = 183.
migration error 0xd4c V2V migration failed : SWAHaulControlOperator with id 'vzm
igrate_v2v_serializer' stage 'CheckParameters' failed : Virtuozzo API function c
all 'VZVolumeMount' failed err = 183
migration finished

Cause

Error code 183 means that VE with the same GUID already exists on the destination node. Such situation could occur if the same VE was restored from backup with different ID or it had been migrated earlier and ID has been changed then.

Resolution

As a workaround the VE can simply be cloned – GUID will be changed in this case – and then migration of the cloned VE will be possible.



FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No