When migrating a VPS from one hardware node to another using 'vzmigrate' an error like this may occur:
#vzmigrate --keep-dst --remove-area no 192.168.0.1 1001
root@192.168.0.1's password:
Connection to destination HN (192.168.0.1) is successfully established
Moving/copying VE#1001 -> VE#1001, [], [] ...
Syncing private area '/vz/private/1001'
- 100% |*****************************|
done
Can't move/copy VE#1001 -> VE#1001, [], [] : can't repair VE#1001 packages : No Match for argument: sendmail-8.13.6-0.FC4.1.i386
No Match for argument: sendmail-cf-8.13.6-0.FC4.1.i386
No Match for argument: sendmail-doc-8.13.6-0.FC4.1.i386
Error: Some packages(s) not found
Loading "rpm2vzrpm" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
ERROR: package manager exited with 1 retcode
The most likely reason for this is a version mismatch in the EZ OS template. It will prevent migrating the VPS even if 'vzmigrate' is run in '-f' mode (force).
- Check if the VPS uses an EZ OS template and which one it is:
# vzpkg list -O 1001
fedora-core-4-x86 2006-12-01 14:41:34
- Check if there are updates available (output shortened):
# vzpkg status
Loading "rpm2vzrpm" plugin
Setting up repositories
Reading repository metadata in from local files
Next update(s) are available:
device-mapper i386 1.02.07-2.0
gnupg i386 1.4.5-1
libtiff i386 3.7.1-6.fc4.3
libuser i386 0.53.7-1.fc4.1
lvm2 i386 2.02.06-1.0.fc4
- Ok, it looks like the template is outdated. Let's make sure our cached template is up-to-date (output shortened).
#vzpkg update cache fedora-core-4-x86
Updating cache for fedora-core-4-x86 OS template
Reading repository metadata in from local files
No Packages marked for Update/Obsoletion
Packing cache file fedora-core-4-x86.tar.gz ...
Cache file fedora-core-4-x86.tar.gz [15M] created.
- Now update the VPS:
#vzpkg update 1001 fedora-core-4-x86
Loading "rpm2vzrpm" plugin
Setting up Update Process
Setting up repositories
[ .. ]
Dependency Updated: samba-common.i386 0:3.0.23a-1.fc4.1
Complete!
Dependency Installed:
gamin i386 0:0.1.1-3.FC4
Updated:
gnupg i386 0:1.4.5-1
python i386 0:2.4.3-8.FC4
samba i386 0:3.0.23a-1.fc4.1
samba-client i386 0:3.0.23a-1.fc4.1
samba-swat i386 0:3.0.23a-1.fc4.1
sendmail i386 0:8.13.7-2.fc4.2
sendmail-cf i386 0:8.13.7-2.fc4.2
sendmail-doc i386 0:8.13.7-2.fc4.2
Dependency Updated:
samba-common i386 0:3.0.23a-1.fc4.1
- If you run 'vzmigrate' using --keep-dst argument log on to your second hardware node first and rename /vz/private/1001 to /vz/private/1001.migrated. (Removing that directory is fine, too, if you're familiar with the process).
- Now run 'vzmigrate' again:
#vzmigrate --keep-dst --remove-area no 192.168.0.1 1001
root@192.168.0.1's password:
Connection to destination HN (192.168.0.1) is successfully established
Moving/copying VE#1001-> VE#1001, [], [] ...
destination '/vz/private/1001' for VE#1001already exists
Syncing private area '/vz/private/1001'
100% |*****************************|
done
Stopping VE#228128 ...
done
Fast syncing private area '/vz/private/1001'
- 100% |*****************************|
done
Starting VE#1001 ...
done
Successfully completedSee, it worked like a charm! :-)
|