Starting with Plesk 12.5, it is possible to upgrade the operating system on a Plesk server. The following dist-upgrade upgrade paths are supported in Plesk:
Warning: If you are running Plesk on a Linux distribution that is not Debian 6 or 7, or Ubuntu 12.04, do not attempt to upgrade the operating system. Such upgrade paths are not supported, and attempting to upgrade will damage your Plesk installation.
Warning: Read the instructions below carefully and follow them closely. Failure to do so may result in Plesk and its services being inoperable.
To perform the dist-upgrade, follow these steps:
distupgrade.helper.<OS.old-OS.new>_pre.sh
and is located in the /usr/local/psa/bin
directory.do-release-upgrade
tool, as described here: https://help.ubuntu.com/14.04/serverguide/installing-upgrading.htmldistupgrade.helper.<OS.old-OS.new>_post.sh
and is located in the /usr/local/psa/bin
directory.After the post-upgrade script finishes, Plesk should be up and running. You can check the upgrade log /var/log/plesk/install/plesk-distupgrade.log for detailed information about the upgrade.
To recover from a failed dist-upgrade, follow these steps:
Check updates for system packages
/etc/apt/sources.list
and the repositories in /etc/apt/sources.list.d/
are switched to the new OS release (i.e. "jessie" if you are upgrading to Debian 8, "wheezy", to Debian 7, and "trusty", to Ubuntu 14).apt-get update
, apt-get upgrade
, and apt-get dist-upgrade
commands. If no packages need to be updated, then the upgrades have already been installed. Otherwise, packages need to be upgraded. See the Upgrade packages section below for details.Check updates for Plesk packages
dpkg -l | less
command. Plesk packages are usually prefixed or suffixed with "plesk-", "psa", or "sw-". Make sure that the version of all Plesk packages contains the name of the OS you are upgrading to (e.g. "debian8" if you are upgrading from Debian 7).Upgrade packages
plesk-installer --skip-cleanup
command (add other options as necessary)./etc/apt/sources.list.d/50sw_autoinstaller.list
will be created./etc/apt/sources.list
and /etc/apt/sources.list.d/*.list
) by replacing the OS codename with the new one, as necessary (i.e. replace "precise" with "trusty", "squeeze" with "wheezy", and "wheezy" with "jessie").apt-get update
command.apt-get upgrade
command.apt-get dist-upgrade
command.apt-get install -f
command to reconfigure the packages that were not installed successfully, fix any errors, and try again.Upgrade Plesk components
Repair Plesk
plesk repair installation
command.plesk repair all -n
command to check for problems with the Plesk configuration.plesk repair mail
or plesk repair web
). If this fails, try fixing the detected issues manually or contact support./etc/apache2/conf.d
and /etc/apache2/plesk.conf.d
still contain the Include
directive with the old syntax. Replace Include
with IncludeOptional
to resolve the issue./etc/apache2/apache2.conf
contains the deprecated LockFile
directive. Replace the lineLockFile ${APACHE_LOCK_DIR}/accept.lock
with the line
Mutex file:${APACHE_LOCK_DIR} default
to resolve the issue.
socache_shmcb.load
file is missing. Run the following commandcp /etc/apache2/mods-available/socache_shmcb.load /etc/apache2/mods-enabled/
to resolve the issue. You should also edit the /etc/apache2/mods-enabled/ssl.conf file and replace the line
SSLMutex file:${APACHE_RUN_DIR}/ssl_mutex
with the line
Mutex file:${APACHE_LOCK_DIR} ssl-cache
to avoid a different issue.
/etc/apache2/conf.d
and /etc/apache2/plesk.conf.d
still contain the deprecated Order
directive. Replace the linesOrder allow,deny
Allow from all
with
Require all granted
to resolve the issue.
/etc/apache2/mods-enabled/dir.conf
is a real file instead of a symlink. Remove the file and create a symlink pointing to /etc/apache2/mods-available/dir.conf
to resolve the issue.init
to systemd
. Restart the server to resolve the issue.