InformationThis article describes steps that will help prevent migration issues.
Most migration issues can be prevented by keeping OS templates up-to-date and having valid repositories for all applications and OS EZ templates.
SymptomsContainer does not start after migration. The similar error is observed:
[root@mypvc ~]# vzctl start 102
Starting the Container ...
Container is mounted
Setting permissions 20002 dev 0x7d00
Set up ioprio: 4
Adding offline management to Container(1): 4643 8443
Adding IP addresses: 10.20.30.40
Error: Unable to execute bash: No such file or directory
Container is unmounted
Failed to start the Container
ResolutionBefore performing a migration, prepare the source and destination Hardware Nodes, as well as the container that is to be migrated:
1. Set SCAN_PRIVATE to "yes" to assure that the "vzpackages" file will include all packages installed in the container. Edit /etc/vztt/vztt.conf on both Nodes:
[root@pvclin47 ~]# grep SCAN_PRIVATE /etc/vztt/vztt.conf
2. Sync packages for the container that is to be migrated:
~# vzpkg sync_vzpackages $CTID
Replace $CTID with the actual container ID value.
3. Also it is useful to do "vzpkg repair" for already migrated container if migration failed before this step. Usually this command is performed automatically during migration:
~# vzpkg repair /vz/private/$CT_ID /etc/sysconfig/vz-scripts/$CTID.conf
NOTE: This works only for PSBM and PVCfL 4.x (4.0.0-520 and later) with containers based on EZ OS templates. Run this command only if it is possible to create new containers based on the OS template.