Customizations That Require Pre-upgrade or Post-upgrade Actions

The following customizations require either pre-upgrade or post-upgrade actions.

Bind-mounting directories under a site's file system

Note: Parallels Pro Control Panel disables sites before upgrading them resulting in loss of bind-mounted directories. If the bind-mounted directory is essential for Parallels Pro Control Panel to proceed with the upgrade, the upgrade fails. This has been observed with the bind-mounted directory /usr/lib/perl.

• Pre-upgrade action required?

  Yes.

  Unmount the bind-mounted directory using the following command:

  umount <dir_name>
  where <dir_name> is the absolute path of the bind-mounted directory.

• Post-upgrade action required?

  Yes. Your bind-mounted directories will be lost. You can bind-mount the directories again using the following command.

  mount -b <dir_to_mnt> <bindmount_dir>

  where:
  <dir_to_mnt> is the absolute path of the directory you want to mount.
  <bindmount_dir> is the absolute path of the location where you want to mount the directory.

Files modified in /usr/lib/opcenter/bind/named_conf_zone.tmpl

• Pre-upgrade action required?

  Yes. Back up the file named_conf_zone.tmpl.

• Post-upgrade action required?

  Yes. Your modifications may be lost after the upgrade. To resolve this issue, re-apply your changes to the file /usr/lib/opcenter/bind/named_conf_zone.tmpl.

PHP binaries installed over files owned by the PHP RPMs

• Pre-upgrade action required?

  Yes. Your custom PHP binaries may be replaced with binaries of the PHP RPM shipped with Parallels Pro Control Panel during the upgrade. To prevent your custom binaries from being replaced during the upgrade, run the script ensim-installer.py with the option --exclude=<pkg1,pkg2,...>. This step prevents the specified packages from getting replaced during the upgrade process.

  For more information on usage of the option, use the --help option with the script.
  For example, to exclude the PHP packages php, php-devel, run the script as follows:
  python ensim-installer.py --exclude=php,php-devel

• Post-upgrade action required?

  No.

Modifications made to the non-config files owned by the RPM database replaced during the upgrade

• Pre upgrade action required?

  Yes. Back up the binaries.

• Post-upgrade action required?

  Yes. Custom-compiled files owned by an RPM (which is part of Parallels Pro Control Panel) may get replaced during the upgrade.

  To see if a file is owned by an RPM, run the command rpm -qf <full_path_of_binary>. If the command returns the name of an RPM, the file is replaced during the upgrade. To ensure compatibility, recompile your binaries, or obtain the appropriate RPMs/source-RPMs that are compatible with the operating system in use.

Modifications made to the file /var/www/html/index.shtml

• Pre-upgrade action required?

  Yes. Back up the file /var/www/html/index.shtml.

• Post-upgrade action required?

  Yes. Modifications made to the Parallels Pro Control Panel root level file /var/www/html/index.shtml may be lost after the upgrade. To resolve this issue, re-apply your changes to the file /var/www/html/index.shtml.

Modifications made to the file /etc/php.ini

• Pre-upgrade action required?

  Yes. Back up the file /etc/php.ini.

• Post-upgrade action required?

  Yes. Modifications made to the /etc/php.ini file may be lost after the upgrade. To resolve this issue, re-apply your changes to the file or restore them from your backup.

Modifications made to the files /etc/httpd/conf/virtual/site<n>

• Pre-upgrade action required?

  Yes. Back up changes to any of the /etc/httpd/conf/virtual/site<n> files.

• Post-upgrade action required?

  Yes. Modifications made to any of the /etc/httpd/conf/virtual/site<n> files may be lost after the upgrade (your changes will be lost even when performing an enable or disable operation). To resolve this issue, you must re-apply the modifications to the files manually.

Modifications made to the files /etc/proftpd/site<n> or /etc/proftpd/site<n>.anonftp

• Pre upgrade action required?

  Yes. Back up your changes to any of the /etc/proftpd/site<n> or /etc/proftpd/site<n>.anonftp files.

• Post-upgrade action required?

  Yes. Modifications made to the files /etc/proftpd/site<n> and /etc/proftpd/site<n>.anonftp are lost after the upgrade (your changes will be lost even when performing an enable or disable operation). To resolve this issue, re-apply your changes to the file or restore them from your backup.

Modifications made to the file /etc/logrotate.conf

• Pre-upgrade action required?

  Yes. Back up the file /etc/logrotate.conf.

• Post-upgrade action required?

  Yes. Modifications to the Parallels Pro Control Panel root level file /etc/logrotate.conf may be lost after the upgrade. To resolve this issue, re-apply your changes to the file or restore them from your backup.

Modifications made to the default Service Plans

• Pre-upgrade action required?

  Yes. Back up the settings of your default Service Plan.

• Post-upgrade action required?

  Yes. The Parallels Pro Control Panel upgrade overwrites the default Service Plan. To resolve this issue, you must restore the Service Plan backup, which you backed up before the upgrade.

Sites that use Microsoft FrontPage Server Extensions in an inconsistent state

• Pre-upgrade action required?

  No.

• Post-upgrade action required?

  Yes. When sites that use Microsoft FrontPage Server Extensions go into an inconsistent state, the following error message is displayed.

  The document root of the web server where you are trying to install the server extensions already contains a disk-based web.

To resolve this issue:

1. Open the file /home/virtual/<domain>/var/www/html/_vti_pvt/service.cnf.
2. Remove the following lines and save your changes.

   vti_httpdversion:SX|FrontPage DBW

   vti_webservertype:SR|diskweb