Unfortunately, even with good preparation, there is always a risk that a service won't start up again, some files go missing or database tables are corrupted. I believe that if you follow these steps you are well prepared, anyway:
Make a full server backup and store it on an external FTP storage.
Then run
# plesk repair all -y
to make sure that the existing Plesk installation is all correctly configured. (Available on 12.5.30)
Then make sure that
- /tmp has at least 3 GB of free disk space (# df -h /tmp)
- root file system / has at least 10% free disk space
- /tmp is not mounted with "noexec" attribute (# mount -l | grep noexec; no output = good, else do # mount -o remount,exec /tmp)
- "base" and "updates" repositories are enabled (# yum reposlist enabled)
- yum can download and install packages from OS vendor's repositories (# yum makecache must yiels 'Metadata Cache Created')
Then apply the latest OS updates on the server (# yum update).
Then run the pre-upgrade check:
# wget
http://autoinstall.plesk.com/PSA_17.0.17/examiners/panel_preupgrade_checker.php
# /usr/local/psa/admin/bin/php panel_preupgrade_checker.php
Do not ignore warnings. Solve underlying issues before you continue by using links to the KB articles provided.
Now do Plesk upgrade. Either follow this guide:
https://support.plesk.com/hc/en-us/...esk-with-the-latest-version-of-autoinstaller- or run the upgrade from "Updates and Upgrades" through GUI.
Various issues can occur after the upgrade. Installation will be logged to/var/log/plesk/install. For further research on issues, check autoinstaller3.log, plesk_17.0.17_installation.log and plesk_17.0.17_installation_problems.log. If upgrade seems to hang, do not interrupt process immediately, but check process tree of parallels_installer process (# ps axfww), wait 3 minutes, check again. Some processes might take a lot of time to complete, depending on your system and computing power.
In case of unclear log messages:
# export PLESK_INSTALLER_DEBUG=1
# plesk installer –select-release-latest –upgrade-installed-components –debug
Then check log files again.