Information

The article describes known issues and limitations of the the PBA for Linux migration from RHEL 4/CentOS 4 to RHEL 6/CentOS 6.

Refer to the main Knowledgebase article #116940 PBA for Linux Migration to RHEL6/CentOS6: Procedure, Known Issues, and Limitations.

PBA for Linux Migration: Known Issues and Limitations

Migration limitations

  1. PVC-based PBA installation may be migrated only between the different PVC hardware nodes.

    The reason is that PVC cannot start 2 containers with the same IP address on the same hardware server.

  2. Destination PBA Application, Database and Online Store servers must reside on different servers, migration of PBA Application and Database server into a single target server is not supported.

  3. The PBA Migration utility does not support passwords containing special characters *, !, ), ( in the config.ini file for PVC-based installation.

  4. Until the bug with id #PBA-52210 fixed, only the English locale is supported on the destination PBA servers.

    Configure the English UTF-8 locale in the /etc/sysconfig/i18n file on all destination PBA servers:

    LANG="en_US.UTF-8"

    Refer to kb #121431 for the details.

  5. There must be at least 10 GB of free diskspace on the / partition on the server where the PBA migration script is being executed.

Migration failures

  1. The pba_migrate script fails with the 'PBA APP configuration failed' error message.

    Resolution: refer to the Parallels Knowledgebase article #115892.

  2. The pba_migrate script fails to connect to PBA servers with the error message 'connection closed' or 'timed out'.

    Resolution: refer to the Parallels Knowledgebase article #116454.

  3. PBA Migration fails with the error message "Can't get PBA version, PBA installed but version format is incorrect".

    Reason: Custom version of some PBA component (Application, Database or Online Store) is installed and the migration utility cannot recognize it as valid.

    Resolution: refer to the Parallels Knowledgebase article #118357.

  4. PBA Migration fails with the '[SSH::Connection] Failure' error message.

    Reason: the PBA Migration script cannot connect to the PBA Application server using SSH.

    Resolution: refer to the Parallels Knowledgebase article #118351.

  5. PBA migration fails with the following error message:

    [2m 36s] [DEBUG] [SSH::Connection] OUT: ; ERR: Usage: pba-installer.bin
[2m 36s] [DIE] [Location] Installer execution failure

    Reason: RPM package of a custom PBA plug-in installed on the source PBA server contains space(s) in the vendor's name like in the example below:

    # rpm --qf '%{NAME} %{VENDOR}\n' -q bm-domreg-plugin-custom
bm-domreg-plugin-custom Custom PBA Plug-in Vendor

    PBA migration script incorrectly parses names of RPM packages in case they contains space(s) in package vendor's name.

    Resolution: re-package custom plug-in with vendor's name without spaces and install it into PBA.

  6. Migration fails with the following diagnostics:

    +0s [ DIE ] [main] Insufficient disk space, at least 10GB required, 5421092 KB available

    Reason: There is no enough disk space on the / partition on the server where the PBA migration script is being executed, the migration script requires at least 10 GB of free diskspace on the / partition.

    Resolution: make sure that there is at least 10 GB of diskspace on the / partition on the migration server.

    In general, the migration server requires as many free diskspace on the partition where the temporary data will be saved (currently it is the / partition) as backup of the PBA database consumes.

    In the future versions of the PBA migration script it will be possible to specify custom location to store temporary files during the migration, request ID is PBA-52726.

Post-migration issues

  1. After migration PBA Application server cannot connect to external network.

    Refer to the Parallels Knowledgebase article #116081 for the resolution.

  2. PBA login page is not displayed after migration, all PBA services are running.

    Check SELinux mode on the PBA Application server, it must be set to permissive. Refer to the Parallels Knowledgebase article #117641 for more details.

  3. If source PBA servers are deployed as PVC containers (VPSs), it is necessary to disable the old containers after the migration is finished in order to prevent accidental startup of the old servers in parallel with the new ones. On Virtuozzo nodes with the old VPSs, use the vzctl utility to disable the source servers, e.g.:

    # vzctl set VPS_ID --save --onboot no --disabled yes

    Replace VPS_ID in the command above with the actual ID of the source PBA VPSs.

  4. PBA customization and custom locale may be broken or not applied after migration.

    Reapply PBA customization saved from the source PBA Application server on the destination server. Follow the PBA documentation to reapply customization:

    PBA Online Store Customization Guide

    PBA UI Customization Guide

    PBA Localization Guide

  5. Custom HTML to PDF conversion tool configured in PBA may not work after migration. As the result customers will not receive invoice notifications from PBA and will not be able to download PDF files with invoices and other documents in the PBA Customer Control Panel.

    1. Install the custom HTML to PDF conversion tool on the destination server after the PBA was migrated.

    2. Alternatively, consider to configure the PDF conversion tool 'htmldoc' shipped with the PBA 5.4 before the migration.

    Refer to the PBA documentation for more information about the PDF conversion tool in PBA - Enabling PDF Conversion.

    Also, read the following Parallels Knowledgebase article - #118448.

  6. PBA services may fail to start after migration with the error message 'Connection refused: 127.0.0.1:5223' in logs.

    Refer to the Parallels Knowledgebase article #118367 for the resolution.

Internal content