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.

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

PHP binaries installed over files owned by the PHP RPMs

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

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

Modifications made to the file /etc/php.ini

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

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

Modifications made to the file /etc/logrotate.conf

Modifications made to the default Service Plans

Sites that use Microsoft FrontPage Server Extensions in an inconsistent state

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