Articles in this section

See more

How to perform dist-upgrade procedure on Linux server with Plesk?

Avatar
Benjamin Weßel
Updated
Follow
Plesk for Linux kb: auxiliary ABT: Group A Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux
  • Plesk for Linux

How to perform a dist-upgrade?

Warning: The dist-upgrade procedure is complex, hence you may want to consider migration instead as can be seen here: Plesk Migration and Transfer Guide

Warning: The dist-upgrade procedure can not be performed in a containerized environment. If this is not known, contact the server provider in order to know if the server or the environment is a container.

The dist-upgrade procedure is supported in Plesk as per the following versions:

Supported for Plesk version
Ubuntu 18 > Ubuntu 20 Plesk Obsidian 18.0.33 and above
Ubuntu 16 > Ubuntu 18 Plesk Obsidian 18.0.30 and above
Debian 9 > Debian 10 Plesk Obsidian 18.0.30 and above

If you have never performed dist-upgrade before, it is recommended to test it first as follows:

  • Install the previous version of OS on a test server or inside a virtual machine. Upgrade it using instructions provided in the documentation by the OS vendor:

    Debian 9 to Debian 10

    Ubuntu 16 to Ubuntu 18

    Ubuntu 18 to Ubuntu 20

  • Solve all potential problems and make sure that Plesk is working after the upgrade. Only after that run the upgrade on the production server.

If you want or need Plesk to assist on this task or to do it on your behalf, it can be requested to Plesk Professional Services team here: Plesk Professional Services: Administrative Services

Ubuntu distributions

Dist-upgrade from Ubuntu 16 to Ubuntu 18

Note: Ubuntu 16 by default has MySQL 5.7 installed, as a result of dist-upgrade it will remain intact and won't be replaced with MariaDB.

Preparing server for upgrade

  1. Create a full server backup. Before the upgrade, make a full server backup (which includes a full backup of all the databases). Also, notify the customers about upcoming downtime of one to three hours.

  2. Remote management module must be installed on the server so that it can still be managed if sshd service cannot be started. Like KVM over IP or IPMI. (This is because, in some tests, sshd service could not be started during the process)

  3. Update the current system to the latest available versions:

    # apt-get update && apt-get upgrade

  4. Add to the mariadb config file /etc/mysql/mariadb.conf.d/50-server.cnf the string innodb_fast_shutdown=0 in the [mysqld] section. In case MySQL is installed, add the string into /etc/mysql/my.cnf in the [mysqld] section.

  5. Restart the DB server to apply changes:

    # systemctl restart mariadb || systemctl restart mysql || systemctl restart mysqld

  6. Remove packages that are no longer supported:

    # apt-get remove samba-common samba-libs samba-vfs-modules

  7. Remove Plesk components that are no longer supported or can break the upgrade:

    Note: Only the bold marked components and packages may be installed back later on this guide

    # apt-get remove psa-watchdog plesk-php52* plesk-php53* plesk-php54* plesk-php55* plesk-php56* plesk-php70* psa-spamassassin docker*

Performing the dist-upgrade

  1. Update source.list file and configure the repository for the OS release that is going to upgrade to, in this case to bionic

    # cat /etc/apt/sources.list
    deb http://archive.ubuntu.com/ubuntu bionic main restricted universe
    deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe
    deb http://security.ubuntu.com/ubuntu bionic-security main restricted universe multiverse
    deb http://autoinstall.plesk.com/PSA_18.0.37/ bionic all
    deb http://autoinstall.plesk.com/ubuntu/PHP70_17 bionic all
    deb http://autoinstall.plesk.com/PHP71_17/ bionic all
    deb http://autoinstall.plesk.com/PHP72_17/ bionic all
    deb http://autoinstall.plesk.com/PHP73_17/ bionic all
    deb http://autoinstall.plesk.com/PHP74_17/ bionic all
    deb http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12 all all
    deb [arch=amd64] http://autoinstall.plesk.com/PMM_0.1.11 bionic all
    deb [arch=amd64] http://autoinstall.plesk.com/NODE_0.0.2 all all
    deb https://packages.grafana.com/oss/deb stable main
    deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable

    Note: The example above is for an installed version of Plesk Obsidian 18.0.37. The correct link for each installed version must be modified accordingly. "sources.list" should be replaced with the contents presented above in the article. Only the highlighted line is to be updated/edited.


    For example: http://autoinstall.plesk.com/PSA_x.y.z/ 

    Whereas the version x.y.z is the current Plesk installed version, which can be found in the output of the command:

    # plesk -v

  2. Update the repositories:

    # apt-get update

  3. Upgrade the kernel:

    # apt-get install linux-generic

  4. Remove from the mariadb config file /etc/mysql/mariadb.conf.d/50-server.cnf the string innodb_fast_shutdown=0 in the [mysqld] section, added at the beginning of this process.

  5. Reboot the server

    # reboot

  6. Update dpkg package:

    # apt-get install dpkg

  7. Update apt package:

    # apt-get install apt

  8. Upgrade all possible packages:

    # apt-get upgrade

  9. When prompted, choose to keep local version config installed for:

    • /opt/psa/etc/apparmor.d/usr.lib.dovecot.dovecot-lda

    • /etc/awstats/awstats.conf

  10. Execute the dist-upgrade process:

    # apt-get dist-upgrade

  11. When prompted, keep the previous version of /etc/apache2/apache2.conf

    Warning: after this operation, apache2 may not start due to problems with http_proxy module.

    1. Disable it by removing file /etc/apache2/mods-enabled/proxy_http.load

      # rm /etc/apache2/mods-enabled/proxy_http.load

    2. Start apache:

      # systemctl start apache2.service

  12. When prompted, keep the local version currently installed for the config files below:

    • /usr/share/rsyslog/50-default.conf

    • /etc/cron.daily/spamassassin

    • /etc/apache2/apache2.conf

    • /etc/pam.d/common-*

    • /etc/rsyslog.d/50-default.conf

    • /usr/share/psa-roundcube/config/config.inc.php

    • /etc/pam.d/common-*

  13. It is safe to install the maintainer's version for the configuration files below when prompted:

    • /etc/apparmor.d/*

    • /etc/ssh/sshd_config

  14. Reboot the server.

    # reboot

  15. Check that Plesk and all its services are working.

Dist-upgrade from Ubuntu 18 to Ubuntu 20

Warning: The dist-upgrade process from Ubuntu 18.04 to Ubuntu 20.04 is supported by Plesk Obsidian 18.0.33 version.

Warning: The dist-upgrade process from Ubuntu 18.04 to Ubuntu 20.04 is supported with MariaDB scenario only.

Preparing server for upgrade

  1. Create a full server backup. Before the upgrade, make a full server backup (which includes a full backup of all the databases). Also, notify the customers about upcoming downtime of one to three hours.

  2. Remote management module must be installed on the server (This is because, in some tests, sshd service could not be started during the process)

  3. Connect and perform the process connected as root or by using the # su - or # sudo su -command.

  4. Uninstall unsupported components like PHP below 7.0, Watchdog (Ubuntu users only)... It can be done through Plesk installer.

    Note: More information can be found here: Software Requirements for Plesk Obsidian

  5. Temporary install msmtp component instead of Postfix. It can be done through Plesk installer or by using the command:

    # plesk installer add --components msmtp

  6. Add to the mariadb config file /etc/mysql/mariadb.conf.d/50-server.cnf the string innodb_fast_shutdown=0 in the [mysqld] section. In case MySQL is installed, add the string into /etc/mysql/my.cnf in the [mysqld] section.

  7. Restart the DB server to apply changes:

    # systemctl restart mariadb || systemctl restart mysql || systemctl restart mysqld

  8. Make sure that   update-manager-core package is installed:

    # apt-get install update-manager-core

  9. Update the current system to the latest available versions:

    # apt-get update && apt-get upgrade

  10. Remove all plesk-related repos from /etc/apt/sources.list.d/. For example, you can archive them by removing originals using the next command:

    # tar -cvf ~apt-sources.tar /etc/apt/sources.list.d/plesk* --remove-files

  11. Stop grafana service:

    # systemctl stop grafana-server.service

Performing the dist-upgrade

  1. Update source.list file and configure the repository for the OS release that is going to upgrade to :

    # cat /etc/apt/sources.list
    deb http://archive.ubuntu.com/ubuntu/ focal main restricted universe
    deb http://archive.ubuntu.com/ubuntu/ focal-updates main restricted universe
    deb http://archive.ubuntu.com/ubuntu/ focal-security main restricted universe
    deb http://autoinstall.plesk.com/PSA_18.0.37/ focal all
    deb http://autoinstall.plesk.com/pool/PHP_7.1.33_96 focal all
    deb http://autoinstall.plesk.com/pool/PHP_7.2.34_150 focal all
    deb http://autoinstall.plesk.com/PHP73_17/ focal all
    deb http://autoinstall.plesk.com/PHP74_17/ focal all
    deb http://autoinstall.plesk.com/PHP80_17/ focal all
    deb https://packages.grafana.com/oss/deb stable main
    deb [arch=amd64] http://autoinstall.plesk.com/PMM_0.1.11 focal all
    deb [arch=amd64] http://autoinstall.plesk.com/NODE_0.0.2 all all
    deb [arch=amd64] http://autoinstall.plesk.com/RUBY_0.0.2 focal all

    Note: The example above is for an installed version of Plesk Obsidian 18.0.37. The correct link for each installed version must be modified accordingly. "sources.list" should be replaced with the contents presented above in the article. Only the highlighted line is to be updated/edited.


    For example: http://autoinstall.plesk.com/PSA_x.y.z/ 

    Whereas the version x.y.z is the current Plesk installed version, which can be found in the output of the command:

    # plesk -v

  2. Update the repositories:

    # apt-get update

  3. Upgrade the kernel:

    # apt-get install linux-generic

  4. Update MariaDB to the next major version provided by the vendor:

    # apt-get install mariadb-server-10.3

    In case MySQL installed, update it to the next major version provided by the vendor

    # apt-get install mysql-server-5.7

  5. Remove from the mariadb config file /etc/mysql/mariadb.conf.d/50-server.cnf the string innodb_fast_shutdown=0 in the [mysqld] section, added at the beginning of this process. In case MySQL is installed, remove the string from /etc/mysql/my.cnf in the [mysqld] section.

  6. Install udev package:

    # apt-get install udev

    Warning: The udev package installation may fail on Ubuntu systems which may be needed to be solved manually. If that is the case, the following should be checked and applied:

    1. At line 26 in the /lib/systemd/system/systemd-udevd.service file, the following string should be changed:

    2. From:

      CONFIG_TEXT: ExecReload=udevadm control --reload --timeout 0

    3. To:

      CONFIG_TEXT: ExecReload=/bin/udevadm control --reload --timeout 0

    4. And execute the following command:

      # apt-get -f install

  7. Install Systemd package:

    # apt-get install systemd

  8. Reboot the server to the new kernel:

    # shutdown -r now

    Note: This will help to avoid problems with services that already loaded old libc6/libstdc libraries

    Warning: MariaDB/MySQL won't start till the reboot is performed.

  9. Remove packages that were installed by dependencies and not needed anymore:

    # apt-get autoremove

  10. Upgrade packages:

    # apt-get upgrade

    Note: If prompted, choose "latest" for LXD if this is unknown.

    Note: When prompted, you should keep the previous version of Spamassassin configuration file.

  11. Remove packages that were installed by dependencies and not needed anymore:

    # apt-get autoremove

  12. Execute the dist-upgrade command:

    # apt-get dist-upgrade

    Note: At this point, plesk-mail-pc-driver, postfix, drweb, kav packages will be removed because there is already a vendor's Postfix that will be used in Ubuntu 20 (which version is lower that the psa-postfix installed in Ubuntu 18)

  13. Remove packages that were installed by dependencies and not needed anymore:

    # apt-get autoremove

  14. Update Plesk to the next available version finishing the dist-upgrade process:

    # plesk installer update

  15. Fix the Bind DNS server defaults file:

    # cp /etc/default/bind9 /etc/default/named

  16. Check that all the Plesk components are installed and if not (Like for example in case there were components uninstalled like the ones in the dist upgrade step), select and re-install them again through the plesk installer along with Postfix which was replaced by msmtp at the beginning:

    # plesk installer

  17. Reboot the server:

    # shutdown -r now

  18. Check that Plesk and all its services are working.

Debian distributions

Dist-upgrade from Debian 9 to Debian 10

Warning: dist-upgrade from Debian 9 to Debian 10 is supported by Plesk Obsidian 18.0.30 version.

Warning: The dist-upgrade process from Debian 9 to Debian 10 is supported with MariaDB scenario only.

Warning: Due to mail server being temporarily uninstalled for the time of upgrade, some settings, i.e. maximum message size, can be reset.

Preparing server for upgrade

  1. Create a full server backup. Before the upgrade, make a full server backup. Also, notify the customers about upcoming downtime of one to three hours.

  2. Connect and perform the process connected as root or by using the # su - or # sudo su -command.

  3. Uninstall unsupported components like docker, PHP below 7.0... (It can be done through Plesk installer).

    Note: More information can be found here: Software Requirements for Plesk Obsidian

  4. Temporary install msmtp component instead of Postfix. It can be done through Plesk installer or by using the command:

    # plesk installer add --components msmtp

  5. Add to the mariadb/mysql config file (Usually /etc/mysql/my.cnf) the string innodb_fast_shutdown=0 in the [mysqld] section.

  6. Restart the DB server to apply changes:

    # systemctl stop mariadb.service ; systemctl start mariadb.service

  7. Update the current system to the latest available versions:

    # apt-get update && apt-get upgrade

  8. Remove all plesk-related repos from /etc/apt/sources.list.d/. For example, you can archive them by removing originals using the next command:

    # tar -cvf ~apt-sources.tar /etc/apt/sources.list.d/plesk* --remove-files

  9. Stop grafana service:

    # systemctl stop grafana-server.service

Performing the dist-upgrade

  1. Update source.list file and configure the repository for the OS release that is going to upgrade to:

    # cat /etc/apt/sources.list
    deb http://security.debian.org/debian-security buster/updates main contrib non-free
    deb http://deb.debian.org/debian/ buster-updates main contrib non-free
    deb http://deb.debian.org/debian/ buster main contrib non-free
    deb http://autoinstall.plesk.com/PSA_18.0.37/ buster all
    deb http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12 all all
    deb http://autoinstall.plesk.com/PHP71_17/ buster all
    deb http://autoinstall.plesk.com/PHP72_17/ buster all
    deb http://autoinstall.plesk.com/PHP73_17/ buster all
    deb http://autoinstall.plesk.com/PHP74_17/ buster all
    deb https://packages.grafana.com/oss/deb stable main
    deb [arch=amd64] http://autoinstall.plesk.com/PMM_0.1.11 buster all
    deb [arch=amd64] http://autoinstall.plesk.com/NODE_0.0.2 all all
    deb [arch=amd64] http://autoinstall.plesk.com/RUBY_0.0.2 buster all

    Note: The example above is for an installed version of Plesk Obsidian 18.0.37. The correct link for each installed version must be modified accordingly.
    "sources.list" should be replaced with the contents presented above in the article. Only the highlighted line is to be updated/edited


    For example: http://autoinstall.plesk.com/PSA_x.y.z/ 

    Whereas the version x.y.z is the current Plesk installed version, which can be found in the output of the command:

    # plesk -v

  2. Update the repositories:

    # apt-get update

  3. Upgrade the kernel:

    # apt-get install linux-image-amd64

  4. Update MariaDB to the next major version provided by the vendor:

    # apt-get install mariadb-server-10.3

    Warning: MariaDB/MySQL won't start till the reboot is performed.

  5. Remove from the mariadb/mysql config file (Usually /etc/mysql/my.cnf) the string innodb_fast_shutdown=0 in the [mysqld] section, added at the beginning of this process.

  6. Reboot the server to the new kernel:

    # shutdown -r now

     

  7. Upgrade packages:

    # apt-get upgrade

    Note: When prompted, you should keep the previous version of Rsyslog configuration file.

    Note: When prompted, you should keep the previous version of Spamassassin configuration file.

  8. Remove packages that were installed by dependencies and not needed anymore:

    # apt-get autoremove

  9. In case AppApmor is enabled adjust it by following this article to let Bind9 load properly

  10. Execute the dist-upgrade command:

    # apt-get dist-upgrade

    Note: At this point, there is a possibility that components are removed, like for example: php7.0-curl plesk-mail-pc-driver postfix psa-drweb-configurator psa-spamassassin which is because on Debian 10 vendor's postfix is used and its version is lower than postfix shipped by Plesk for Debian 9

  11. Update Plesk to next available version finishing the dist-upgrade process:

    # plesk installer update

  12. Check that all the Plesk components are installed and if not (Like for example in case there were components uninstalled like the ones in the dist upgrade step), select and re-install them again through the plesk installer along with Postfix which was replaced by msmtp at the beginning:

    # plesk installer

  13. Reboot the server:

    # reboot

  14. Check that Plesk and all its services are working.

  15. Use the following commands to regenerate web server as well as DNS configuration files if needed:

    # plesk repair web

    # plesk repair dns

Warning: Most APS applications will not work with PHP 7.x

Unsupported EOLed OSes 

Note: Plesk Onyx 17.8 is EOLed and no support will be provided if something goes wrong. In case you have  EOLed OS/Plesk the best-recommended scenario is migration.

Dist-upgrade from Ubuntu 14 to Ubuntu 16

Warning: dist-upgrade from Ubuntu 14 to Ubuntu 16 and is supported by Plesk Onyx 17.8 version.

Warning: During an upgrade from Ubuntu 14 to Ubuntu 16, system PHP 5.x shipped by OS vendor will be upgraded to PHP 7.x. So to avoid any PHP compatibility issues, before an upgrade, it is highly recommended to switch all sites having PHP handler 5.x by OS vendor to corresponding custom PHP handlers. Please refer to these KB articles for details: How to configure PHP handlers in Plesk for Linux? and How to apply new PHP handler to multiple domains via CLI?

Warning: Also, MySQL server upgrade can fail during the upgrade. The issue and its resolution are described in: Dist-upgrade from Ubuntu 14 to 16 fails: Sub-process /usr/bin/dpkg returned an error code (1).

Warning: if PHP by OS vendor was updated from third-party sources prior to dist-upgrade, it may break webmail functionality.

  1. Create a full server backup. Before the upgrade, make a full server backup. Also, notify the customers about upcoming downtime of one to three hours.

  2. Run below script and follow the wizard:

    # /opt/psa/bin/distupgrade.helper.ubt14-ubt16.x64.sh

    The script logs all its actions in /var/log/plesk/install/plesk-distupgrade.log .

  3. During the script execution, you will be asked to reboot the server. Reboot the server.

  4. After the server reboot, run the script once again.

Dist-upgrade from Debian 8 to Debian 9

Warning: dist-upgrade from Debian 8 to Debian 9 is supported by Plesk Onyx 17.8 version.

Warning: if PHP by OS vendor was updated from third-party sources prior to dist-upgrade, it may break webmail functionality.

Preparing server for upgrade

  1. Create a full server backup. Before the upgrade, make a full server backup. Also notify the customers about upcoming downtime of one to three hours.

  2. Consider to remove sources list backup files which might be left from the previous dist-upgrade:

    • /etc/apt/sources.list.saved_by_plesk_distupgrade
    • /etc/apt/sources.list.d/50sw_autoinstaller.list.saved_by_plesk_distupgrade`

  3. Run pre-upgrade helper script and prepare Plesk and the system for the upgrade:

    # /opt/psa/bin/distupgrade.helper.deb8-deb9_pre.x64.sh

    The script logs all its actions in /var/log/plesk/install/plesk-distupgrade.log.

Performing the dist-upgrade

  1. Update source.list file and configure the repository for the OS release that is going to upgrade to:

    # cat /etc/apt/sources.list
    deb http://deb.debian.org/debian stretch main contrib non-free
    deb http://security.debian.org/debian-security/ stretch/updates main contrib non-free
    deb http://deb.debian.org/debian stretch-updates main contrib non-free

  2. Update information about system packages:

    # apt-get update

  3. Upgrade the system:

    # /opt/psa/bin/distupgrade.helper.deb8-deb9.x64.sh

    This command will perform a complete upgrade of the system, install the newest available versions of all packages and resolve all possible dependency changes between packages in different releases.

    During the upgrade the system might produce prompts like:

    CONFIG_TEXT: Configuration file /etc/mysql/my.cnf
    ==> Modified (by you or by a script) since installation.
    ==> Package distributor has shipped an updated version.
    What would you like to do about it ?
    Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
    D : show the differences between the versions
    Z : start a shell to examine the situation
    The default action is to keep your current version.
    *** my.cnf (Y/I/N/O/D/Z) [default=N] ?

    Choose to replace configuration files with a new one (answer Y).

Finalizing the upgrade

  1. Run post-upgrade helper script:

    # /opt/psa/bin/distupgrade.helper.deb8-deb9_post.x64.sh

    Note: This script is already called during the execution of /opt/psa/bin/distupgrade.helper.deb8-deb9.x64.sh, run it to verify that everything was successfully done. Its actions are logged in /var/log/plesk/install/plesk-distupgrade.log too.

  2. Reboot the server.

  3. Check that Plesk and all its services are working.

Comments

98 comments

Sort by Date Votes
  • Avatar
    Jan Bludau

    How to make a dist-upgrade from Plesk 17.8.11 i can't find the dist-upgrade helper script on the mentationed position.

    0
    Comment actions Permalink
  • Avatar
    Nikita Nikushkin

    Hi @Jan Bludau,

    Could please provide us with the OS?

    Thank you!

    0
    Comment actions Permalink
  • Avatar
    Oliver Mueller

    Still no migration path for Ubuntu 16.04 to 18.04? It is almost a year ago, that Ubuntu 18.04 is supported by Plesk (fresh installation). Is there any ETA on this topic? A migration to another server with fresh installed plesk is no option for us. We really need this upgrade/migration.

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oliver,

    Thank you for the feedback.

    I will need some time to clarify if there's the exact ETA.

    Me or my colleague will let you know when receive the information.

    0
    Comment actions Permalink
  • Avatar
    Oliver Mueller

    Still no ETA? Even an approximation would help.

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oliver,

    I will clarify the plans for this functionality and will update write to them here, after I'll get any news.

    -1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oliver,

    According to the information I got, the Development team still has plans to implement this functionality.

    The ETA will be available later. 

    News will be added to this article.

    -1
    Comment actions Permalink
  • Avatar
    Elisabeth Kahnert

    Upgrade from Ubuntu 16 to Ubuntu 18 is needed

    1
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    @Elisabeth,

    Currently, Plesk does not support dist-upgrade from Ubuntu 16.04 to Ubuntu 18.04 yet. Dist-upgrade support from Ubuntu 16.04 to Ubuntu 18.04 to Plesk, will be added in a future product update.

    -2
    Comment actions Permalink
  • Avatar
    Elisabeth Kahnert

    @Julian Bonpland Mignaquy

    Yes, and this text is more than 1 year old.

    1
    Comment actions Permalink
  • Avatar
    Sandonanet s.n.c.

    Hi, i have Ubuntu 14.04.6 LTS‬ with Plesk Onyx Version 17.8.11 and i want upgrade my system to ubuntu 16.04 LTS.

    I have performed the procedure you indicated and run the script /opt/psa/bin/distupgrade.helper.ubt14-ubt16.x64.sh

    The procedure is performed correctly except the update of mysql 5.5 to 5.7 which remains an error.

    I have restored the initial backup of the machine and retried the procedure several times but the error persists.

    I also tried to manually update mysql from version 5.5 to 5.6 but the procedures I found on the net do not work.

    Can anyone help me? Thank you

     

     

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Sandonanet s.n.c.,

    Try steps for Debian from this article: https://support.plesk.com/hc/en-us/articles/213403429-How-to-upgrade-MySQL-5-5-to-5-6-5-7-or-MariaDB-5-5-to-10-0-10-1-10-2-on-Linux-

    In case this wouldn't help, I can suggest preparing a new server with the required OS, install fresh Plesk and migrate domains: https://support.plesk.com/hc/en-us/articles/213912645-Plesk-Migration-and-Transfer-Guide

    These operations may also be done on a paid basis by Plesk Professional services team: https://www.plesk.com/professional-services/

    0
    Comment actions Permalink
  • Avatar
    Dirk Riehle

    +1 for getting an upgrade path from Ubuntu 16.04 to 18.04. It is about time.

    1
    Comment actions Permalink
  • Avatar
    Oliver Mueller

    Is there any news about the upgrade capability from Ubuntu 16.04 to 18.04? Some status or progress information? An idea of an ETA?

     

    Ubuntu 20.04 is coming out in 3 weeks and yet, there is not upgrade to its predecessor. This is really disappointing. So we customer can expect that an upgrade to 20.04 will arrive in 2022 or later? It is really frustrating to be forced to work with such an old system. Currently it is 4 years old. Many Ubuntu packages are really outdated and even though it is an LTS and Ubuntu delivers at least security packages, this is NOT true for all packages. In fact the very most packages are not included within this support. Basically our server is running with a lot of very outdated and unsupported packages now. This is a big security problem:

    # ubuntu-support-status --show-unsupported
    Support status summary of 'plesk-server':

    You have 714 packages (62.2%) supported until April 2021 (Canonical - 5y)
    You have 3 packages (0.3%) supported until April 2021 (Community - 5y)

    You have 153 packages (13.3%) that can not/no-longer be downloaded
    You have 277 packages (24.1%) that are unsupported
    1
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy (Edited )

    @Oliver Dirk Riehle Hi! So far there is no ETA for Ubuntu 16 to 18. At the moment we can recommend deploying a new server with Ubuntu 18 and migrating using Plesk Migrator.

    -2
    Comment actions Permalink
  • Avatar
    Oliver Mueller (Edited )

    @Julian: An upgrade path using the plesk migrator is not a real option for us and for many others either.

    We have many customers using their own DNS. Coordinating a synchronous switch with them is a huge effort and will result in a lot of trouble. Economically it just doesn't make sense to us. As Plesk customer we expected to get a "smooth" migration path and not a bumpy ride with the Plesk Migrator. And DNS is not the only trouble doing that.

    Is there going to be an upgrade path from 16.04 directly to 20.04? So you have basically discontinued support for a server OS upgrade? Is that correct?

    @ivan said, that more infos on this topic is expected in Q1 2020 (https://support.plesk.com/hc/en-us/articles/360002913773/comments/360000940499)

     

    2
    Comment actions Permalink
  • Avatar
    Michael

    +1

    I am also waiting for this upgrade support!

    Buying and setting up a new server is way too much effort.

    2
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Oliver Mueller and Michael

    Thank you for the feedback.

    > We have many customers using their own DNS. Coordinating a synchronous switch with them is a huge effort and will result in a lot of trouble. Economically it just doesn't make sense to us. As Plesk customer we expected to get a "smooth" migration path and not a bumpy ride with the Plesk Migrator. And DNS is not the only trouble doing that.

    Dist-upgrade is known as a riskier approach, which sometimes leads to server inaccessibility or other issues. Even for a scenario when dist-upgrade is possible, migration is recommended. There's a way to avoid making customers reconfiguring DNS: after migration, the new server's IP may be changed to the same as was on the old one (https://support.plesk.com/hc/en-us/articles/115001761193-How-to-change-the-IP-address-of-Plesk-server-).

     

    > Is there going to be an upgrade path from 16.04 directly to 20.04? 

    There're no such plans.

     

    > more infos on this topic is expected

    RnD was concentrated on CentOS 8 support which took more resources when expected. So, more precise data is t be available later.

    Thank you for understanding.

    -2
    Comment actions Permalink
  • Avatar
    Jan Bludau

    +1

    i'm waiting for CentOS 8 Upgrade from CentOS 7 :-)

    0
    Comment actions Permalink
  • Avatar
    François-Xavier Guénan

    I've successfully upgraded from Ubuntu 14 to 16 using the script, but after the first reboot, I had to boot using network (OVH net-boot) to keep the update running, otherwise it was booting to emergency mode. Now everything runs fine, but only on net-boot. If I boot using harddrive I'm back to emergency mode. I'll edit my post when I'll fix this.

    0
    Comment actions Permalink
  • Avatar
    Vương Công Minh (Edited )

    I find that Ubuntu 18.04 supports upgrading from 16.04 through do-release-upgrade. You can review how to upgrade to the new version

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Vương Công Minh

    Mind you, this wasn't tested on Plesk side.

    Consider upgrading the test server before production one.

    Also, I would suggest making a server snapshot before the upgrade.

    -1
    Comment actions Permalink
  • Avatar
    putinluver127

    This feature is promised for 22 month and is a long-term feature in Debian based derivates. Making a uservoice out of it is just typical for you useless putin alt-right loving a-holes

    Plesk

    put a toothpick under your big ducking ugly toes and kick a wall you senseless piece of 💩's...

    2
    Comment actions Permalink
  • Avatar
    Mark-Oliver Wolter (Edited )

    Similar problem as Μίστερ Μολ also trying to upgrade from jessie to stretch.

    /opt/psa/bin/distupgrade.helper.deb8-deb9.x64.sh results in:

    START Distupgrade
    START Distupgrade

    File '/etc/apache2/ports.conf.saved_by_plesk_distupgrade_from_jessie' exists. Skip saving '/etc/apache2/ports.conf'.
    '/etc/apt/sources.list' has been already updated. Skip.
    '/etc/apt/sources.list.d/dotdeb.list' has been already updated. Skip.
    '/etc/apt/sources.list.d/plesk-ext-panel-migrator.list' has been already updated. Skip.
    '/etc/apt/sources.list.d/plesk.list' has been already updated. Skip.
    Now you can perform dist-upgrade to stretch using any method you like.
    You can visit https://www.debian.org/releases/stretch/amd64/release-notes/ch-upgrading.html for more information.
    After system dist-upgrade is finished run '/opt/psa/bin/distupgrade.helper.deb8-deb9_post.x64.sh'.
    [...]
    0 upgraded, 0 newly installed, 0 to remove and 137 not upgraded.
    Hit:1 http://autoinstall.plesk.com/PMM_0.1.11 stretch InRelease
    Hit:2 http://security.debian.org stretch/updates InRelease
    Hit:4 http://autoinstall.plesk.com/debian/PSA_17.8.11 jessie InRelease
    Hit:5 http://autoinstall.plesk.com/debian/PHP70_17 jessie InRelease
    Hit:6 http://autoinstall.plesk.com/PHP71_17 jessie InRelease
    Ign:3 http://cdn-fastly.deb.debian.org/debian stretch InRelease
    Hit:7 http://cdn-fastly.deb.debian.org/debian stretch Release
    Reading package lists...
    Reading package lists...
    Building dependency tree...
    Reading state information...
    E: Unable to locate package psa-php-configurator
    Some error during dist-upgrade middle stage have occurred.
    Check /var/log/plesk/install/plesk-distupgrade.log for error details.
    Visit https://docs.plesk.com/en-US/current/administrator-guide/server-administration/distupgrade-support.74627/ for information about troubleshooting and recovering from failed dist-upgrade.
    STOP Distupgrade

    "Check /var/log/plesk/install/plesk-distupgrade.log for error details" is useless. That IS the content of the file.

    Obviously, at this stage, apt only knows about the psa-php5-configurator, but not psa-php-configurator.

    So this is didn't quite work as intended:

    '/etc/apt/sources.list.d/plesk.list' has been updated: 'jessie' is replaced with 'stretch'. Original file is saved in '/etc/apt/plesk.list.saved_by_plesk_distupgrade_from_jessie'.

    The file /etc/apt/plesk.list.saved_by_plesk_distupgrade_from_jessie contains lines that were not in my /etc/apt/sources.list.d/plesk.list before calling the upgrade script (e.g. deb http://autoinstall.plesk.com/debian/PHP52_17 jessie all) and the plesk.list afterwards is still all jessie:

    ## Persistent repositories for Plesk Products.
    deb http://autoinstall.plesk.com/debian/PSA_17.8.11 jessie extras
    deb http://autoinstall.plesk.com/debian/PHP70_17 jessie all
    deb http://autoinstall.plesk.com/PHP71_17/ jessie all

    Turns out what happened is:

    Before the upgrade, I used Tools&Settings->Plesk->Updates and Upgrades to remove the PHP5.6 packages. Thing is, the autoinstaller also messes with the sources.list.d files and inserts its own 50sw_autoinstaller.list and plesk.list. And as the autoinstaller has no logout function (at least I can't find it), this is a timebomb that triggers 30 minutes after the last action, removing 50sw_autoinstaller.list and replacing the old plesk.list. The upgrade helper script also places a 50sw_autoinstaller.list in there, so when autoinstaller exits, it removes a file that is still needed and changes the contents of the other.

    Would be nice if "Updates and Upgrades" had a "quit autoinstaller" button and if the helper script refused to run while autoinstaller is active.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Mark-Oliver Wolter

    Thank you for sharing your user experience. Feel free to create feature suggestions at our Plesk UserVoice: https://plesk.uservoice.com/

    The top-ranked suggestions are likely to be included in future updates.

    Meanwhile, we'll think about how to improve this article.

    -1
    Comment actions Permalink
  • Avatar
    B Pfleging

    Hello @Ivan Postnikov is there still no ETA for the dist-upgrade from Ubuntu 16.04 to 18.04? Given that 20.04 is now already available, that step is clearly overdue.

    Given the most recent announcement of again increasing prices, I guess this is clearly something we can expect from a product where prices are continuously rising.

    Best regards,

    1
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello,

    We do plan to publish a guide for Ubuntu dist-upgrade16>18 and 18>20 on Plesk Obsidian 18.0.31 version approximately till end of October.

    2
    Comment actions Permalink
  • Avatar
    B Pfleging

    Sounds great Anton Maslov. One more day if you do not want to break your (flexible) promise...

    1
    Comment actions Permalink
  • Avatar
    Adrian Czternasty (Edited )

    Hi 

    I have also issues with upgrading Debian from v.8 to v.9 and also each day I have received an email with an error regarding PHP 7.3.17 like this below:

    Reason: 2020-11-04 06:26:18 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
    2020-11-04 06:26:40 ERROR: W:Failed to fetch http://autoinstall.plesk.com/PHP73_17/dists/jessie/all/binary-amd64/Packages 404 Not Found
    , W:Failed to fetch http://autoinstall.plesk.com/PHP73_17/dists/jessie/all/binary-i386/Packages 404 Not Found
    , E:Some index files failed to download. They have been ignored, or old ones used instead.
    2020-11-04 06:26:40 ERROR: Exited with returncode 1.

    And the same error was during the upgrade, after the while, I figured out that the root cause was unused and installed on the VPS the PHP5 by OS Vendor in Plesk Updates and Upgrades. On VPS I use only PHP 7.4 so, why the error shows PHP 7.3.17 and deinstalling PHP 5 fix this, I do not know, but the upgrading from Debian 8 to Debian 9 start doing the job.

    Maybe it will some helps.

    Regards

    0
    Comment actions Permalink
  • Avatar
    Muhamed Osmani

    Vote here for dist-upgrade Support Debian 9 > Debian 10:

    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/41876701-support-dist-upgrade-debian-9-stretch-debian-1

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles