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

Updated February 07, 2025 20:52

Plesk for Linux kb: technical Plesk Obsidian for Linux ABT: Group A

Applicable to:

Plesk for Linux

How to perform a dist-upgrade?

Warning: The dist-upgrade procedure is complex, hence you may want to consider migrating instead as explained in Plesk Migration and Transfer Guide.

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

Warning: For servers running Plesk versions below 18.0.45, always use Plesk-Archive repository in sources.list file by replacing "autoinstall.plesk.com" with "autoinstall-archives.plesk.com" in the following instructions

Warning: The dist-upgrade process cannot be performed on containers due technical limitations. By design a container virtualization does not contain operating system images but instead use a shared base OS while isolates applications/services only.

The dist-upgrade procedure is supported for the following Plesk versions and operating systems:

Supported for	Plesk version
Ubuntu 22 > Ubuntu 24	Plesk Obsidian 18.0.61 and above
Ubuntu 20 > Ubuntu 22	Plesk Obsidian 18.0.44 and above
Ubuntu 20 on ARM > Ubuntu 22 on ARM	Plesk Obsidian 18.0.46 and above
Ubuntu 18 > Ubuntu 20	Plesk Obsidian 18.0.33 and above
Ubuntu 16 > Ubuntu 18	Plesk Obsidian 18.0.30 and above
Debian 11 > Debian 12	Plesk Obsidian 18.0.57 and above
Debian 10 > Debian 11	Plesk Obsidian 18.0.42 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 the 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 Plesk is working after the upgrade before proceeding with the upgrade on the production server.

If you want or need Plesk to assist on this task or to do it on your behalf, place a request to Plesk Professional Services team here: Plesk Professional Services: Administrative Services

Ubuntu distributions

Dist-upgrade from Ubuntu 22 (Jammy Jellyfish) to Ubuntu 24 (Noble Numbat) - Manual step by step process

Warning: The dist-upgrade process from Ubuntu 22.04 to Ubuntu 24.04 is supported on x64 CPUs from Plesk Obsidian 18.0.61 version and later.

Warning: Plesk Premium Email extension depends on Kolab which does not yet support Ubuntu 24. Remove the extension before proceeding with the dist-upgrade.

Preparing server for upgrade

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
Connect to the server via SSH
Change to root user by using the following command:

# sudo su -
Remove packages which were installed by dependencies but are not required:

# apt-get autoremove
Execute the command below to be sure that system is up-to-date:

# plesk sbin pum --update
Run the command to make Plesk up-to-date:

# plesk installer update
Install aptitude:

# apt-get install aptitude
Remove repository lists that are related to Plesk:

# rm -f /etc/apt/sources.list.d/plesk*.list

Performing the dist-upgrade
Replace 'jammy' sources lists with 'noble' sources lists in /etc/apt/sources.list and /etc/apt/sources.list.d/*.list:

# sed -i "s/jammy/noble/g" /etc/apt/sources.list

Note: below is the example for /etc/apt/sources.list file:

deb http://archive.ubuntu.com/ubuntu noble main restricted universe
deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe
deb http://security.ubuntu.com/ubuntu noble-security main restricted universe multiverse
Make installer to create Plesk sources list for Ubuntu 24.04:

# plesk installer --override-os-version 24.04 --check-updates --skip-cleanup
Change bind-address in the /etc/mysql/my.cnf to accept IPv4 connections (From 10.6.0 :: refers to IPv6 stictly):

bind-address = ::ffff:127.0.0.1

to

bind-address = 127.0.0.1
Add the string below into the /etc/mysql/my.cnf file under [mysqld] section:

innodb_fast_shutdown=0
Restart MariaDB/MySQL service to apply the changes:

# systemctl restart mariadb || systemctl restart mysql
Install modern kernel, libc6, python3, mariadb packages with the command:
- For MariaDB:
  
  # aptitude install base-files linux-generic libc6 python3 mariadb-server
- For MySQL:
  
  Note: In case that the server already runs a higher version of MySQL than 8.0, remove mysql-server-8.0 from the below command before run.
  
  # aptitude install base-files linux-generic libc6 python3 mysql-server-8.0
Note: Make sure that after execution of the command above, Plesk-related packages are not marked for removal. Normally if mariadb server is installed the list should be as below:

Remove the following packages:
1. chrony [4.2-2ubuntu2 (now.]
2. libssl3 [3.0.2-0ubuntu1.15 (now.]
3. mariadb-client-10.6 [1:10.6.16-0ubuntu0.22.04.1 (now.]
4. mariadb-client-core-10.6 [1:10.6.16-0ubuntu0.22.04.1 (now.]
5. mariadb-server-core-10.6 [1:10.6.16-0ubuntu0.22.04.1 (now.]

Note: When a request to overwrite SSHd configuration appears, select to leave the configuration as it is.

Note: Select to allow automatic restart for services
Remove line below from the /etc/mysql/my.cnf file:

innodb_fast_shutdown=0
Reboot the server:

# reboot
Wait some time for the server to reboot, then connect to the server via SSH
Switch to root user:

# sudo su -
Execute the command below to get Plesk build for Ubuntu 24.04:

# plesk installer update --skip-cleanup
Update the Plesk extensions:

# plesk bin extension -l | egrep '(panel-migrator|site-import|docker|grafana)'| awk {'print $1'} | xargs -i plesk bin extension -i {}
Complete distupgrade process:

# apt-get dist-upgrade

Note: leave the configurations for Postfix, PAM, rsyslog, SpamAssassin, cloud-init and other services as is.
Optional step: Remove unused packages:

# apt-get autoremove
Optional step: Purge the configuration files of the removed packages:

# apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`
Restore the Plesk packages configuration:

# plesk installer update
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server:

# reboot
Wait some time for the server to reboot and check that Plesk and all its services are working.

Dist-upgrade from Ubuntu 20 (Focal Fossa) to Ubuntu 22 (Jammy Jellyfish) - Automated tool process

Preparing server for upgrade: To avoid downtime and data loss, make sure you have read and understood the following information before using the utility:

Create a full server backup: Before the upgrade, make a full server backup (which includes a full backup of all the databases). It's strongly recommend to create a snapshot as a recovery point in case the conversion process fails.
Remote management module must be installed on the server, because in some tests the sshd service could not be started during the process.
Server runs the latest version of Plesk
Notify the customers about upcoming downtime. Expected downtime is 20-30 minutes where server reboots one or more times (Plesk services, hosted websites, and emails will be unavailable).
Requirements: grub boot is installed, server has at least 5 GB of free disk space and at least 2 GB of installed RAM.
Read the list of Known issues or limiters for the tool here.

Using the tool to upgrade from Ubuntu 20 to Ubuntu 22:

Connect to the server via SSH as root or other sudoer user and run sudo su -.
Download and extract the latest tool version into the server:

# wget https://github.com/plesk/ubuntu20to22/releases/download/v1.0.0/ubuntu20to22-1.0.0.zip
# unzip ubuntu20to22-1.0.0.zip
# chmod 755 ubuntu20to22
In order to monitor the conversion process, we recommend using the 'screen' utility to run the tool in the background with the following command:

# screen -S ubuntu20to22

3.1 Run the tool convert stage by running the tool with the next command. Note that this process may reboot the server a several times:

# ./ubuntu20to22

Note: In case the SSH connection to the server is lost, reconnect to the screen session by running screen -r ubuntu20to22
Reconnect to the server after the convert stage completes (around 20-30 minutes) and monitor the finish stage with:

# ./ubuntu20to22 --status

or

# ./ubuntu20to22 --monitor
- Alternatively the status can be tracked by checking the log file at /var/log/plesk/ubuntu20to22.log. Once the process completes the following message will be observed:
  
  Message from the Plesk ubuntu20to22 tool:
  The server has been upgraded to Ubuntu 22.
  You can remove this message from the /etc/motd file.

Note: If the process was interrupted before the first reboot, restart it with ./ubuntu20to22 --resume option. If the interruption was after the first reboot, restart the process running systemctl restart plesk-dist-upgrader.

Note: If the operation fails before the distupgrade performs during the conversion stage, run ./ubuntu20to22 --revert to restore Plesk to normal operation. The tool will attempt to undo some of the changes it made and restart Plesk services. Once the root cause of the failure be solved try the conversion again.

Warning: Revert cannot be used to undo the changes after the distupgrade take place because packages provided by Ubuntu 22 already installed. Check the status of the conversion process and monitor its progress

Dist-upgrade from Ubuntu 20 (Focal Fossa) to Ubuntu 22 (Jammy Jellyfish) - Manual step by step process

Warning: The dist-upgrade process from Ubuntu 20.04 to Ubuntu 22.04 on x64 CPUs is supported by Plesk Obsidian 18.0.44 version. The dist-upgrade process from Ubuntu 20.04 to Ubuntu 22.04 on ARM CPUs is supported by Plesk Obsidian 18.0.46 version.

Preparing server for upgrade

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
Connect to the server via SSH
Change to root user by using the following command:

# sudo su -
Enable enhanced security mode:

# plesk bin passwords --encrypt
Uninstall the unsupported components Mailman and PHP handlers below version 7.3:

# plesk installer remove --components php7.1 php7.2 php7.3 mailman
Remove packages which were installed by dependencies but are not required:

# apt-get autoremove
Execute the command below to be sure that system is up-to-date:

# plesk sbin pum --update
Run the command to make Plesk up-to-date:

# plesk installer update
Install aptitude:

# apt-get install aptitude
Remove repository lists that are related to Plesk:

# rm -f /etc/apt/sources.list.d/plesk*.list

Performing the dist-upgrade
Replace focal sources lists with jammy sources lists in /etc/apt/sources.list and /etc/apt/sources.list.d/*.list:

# sed -i "s/focal/jammy/g" /etc/apt/sources.list

Note: below is the example for /etc/apt/sources.list file:

deb http://archive.ubuntu.com/ubuntu jammy main restricted universe
deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe
deb http://security.ubuntu.com/ubuntu jammy-security main restricted universe multiverse
Make installer to create Plesk sources list for Ubuntu 22.04:

# plesk installer --override-os-version 22.04 --check-updates --skip-cleanup
Change bind-address in the /etc/mysql/my.cnf to accept IPv4 connections (From 10.6.0 :: refers to IPv6 stictly):

bind-address = ::ffff:127.0.0.1

to

bind-address = 127.0.0.1
Add the string below into the /etc/mysql/my.cnf file under [mysqld] section:

innodb_fast_shutdown=0
Restart MariaDB/MySQL service to apply the changes:

# systemctl restart mariadb || systemctl restart mysql
Install modern kernel, libc6, python3, mariadb packages with the command:

Note: mysql-community-server has not been published for Ubuntu 22.04 Jammy yet.
- For MariaDB:
  
  Note: In case that the server already runs a higher version of MariaDB than 10.6, remove mariadb-server-10.6 from the below command before run.
  
  # aptitude install base-files linux-generic libc6 python3 mariadb-server-10.6
- For MySQL:
  
  Note: In case that the server already runs a higher version of MySQL than 8.0, remove mysql-server-8.0 from the below command before run.
  
  # aptitude install base-files linux-generic libc6 python3 mysql-server-8.0
Note: Make sure that after execution of the command above, Plesk-related packages are not marked for removal. Normally if mariadb server is installed the list should be as below:

Remove the following packages:
1. galera-3 [25.3.29-1 (now)]
2. mariadb-client-10.3 [1:10.3.34-0ubuntu0.20.04.1 (now)]
3. mariadb-client-core-10.3 [1:10.3.34-0ubuntu0.20.04.1 (now)]
4. mariadb-server-10.3 [1:10.3.34-0ubuntu0.20.04.1 (now)]
5. mariadb-server-core-10.3 [1:10.3.34-0ubuntu0.20.04.1 (now)]
6. python3-systemd [234-3build2 (now)]
7. python3-twisted-bin [18.9.0-11ubuntu0.20.04.2 (now)

Note: When a request to overwrite SSHd configuration appears, select to leave the configuration as it is.

Note: Select to allow automatic restart for services
Remove line below from the /etc/mysql/my.cnf file:

innodb_fast_shutdown=0
Reboot the server:

# reboot
Wait some time for the server to reboot, then connect to the server via SSH
Switch to root user:

# sudo su -
Execute the command below to get Plesk build for Ubuntu 22.04:

# plesk installer update --skip-cleanup
Update the Plesk extensions:

# plesk bin extension -l | egrep '(panel-migrator|site-import|docker|grafana)'| awk {'print $1'} | xargs -i plesk bin extension -i {}
Complete distupgrade process:

# apt-get dist-upgrade

Note: leave the configurations for Postfix, PAM, rsyslog, SpamAssassin, cloud-init and other services as is.
Optional step: Remove unused packages:

# apt-get autoremove
Optional step: Purge the configuration files of the removed packages:

# apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`
Restore the Plesk packages configuration:

# plesk installer update
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server:

# reboot
Wait some time for the server to reboot and check that Plesk and all its services are working.

Dist-upgrade from Ubuntu 18 (Bionic Beaver) to Ubuntu 20 (Focal Fossa) - Automated tool process

Preparing server for upgrade: To avoid extra downtime and/or data loss, make sure to read and understand the following information before using the distupgrade tool:

Create a full server backup: Before the upgrade, make a full server backup (which includes a full backup of all the databases). It's strongly recommend to create a snapshot as a recovery point in case the conversion process fails.
Remote management module must be installed on the server, because in some tests the sshd service could not be started during the process.
Server runs the latest version of Plesk
Notify the customers about upcoming downtime. Expected downtime is 20-30 minutes where server reboots one or more times (Plesk services, hosted websites, and emails will be unavailable).
Requirements: grub boot is installed, server has at least 5 GB of free disk space and at least 2 GB of installed RAM.
Read the list of Known issues or limiters for the tool here.
Once downloaded check the general stages of the tool with ./ubuntu18to20 --help and the detailed plan with ./ubuntu18to20 --show-plan output. More information can be found here.

Using the tool to upgrade from Ubuntu 18 to Ubuntu 20:

Connect to the server via SSH as root or other sudoer user and run sudo su -.
Download and extract the latest tool version into the server:

# wget https://github.com/plesk/ubuntu18to20/releases/download/v2.1.2/ubuntu18to20-2.1.2.zip
# unzip ubuntu18to20-2.1.2.zip
# chmod 755 ubuntu18to20
In order to monitor the conversion process, we recommend using the 'screen' utility to run the tool in the background with the following command:

# screen -S ubuntu18to20

3.1 Run the tool convert stage by running the tool with the next command. Note that this process may reboot the server a several times:

# ./ubuntu18to20

Note: In case the SSH connection to the server is lost, reconnect to the screen session by running screen -r ubuntu18to20
Reconnect to the server after the convert stage completes (around 20-30 minutes) and monitor the finish stage with:

# ./ubuntu18to20 --status

or

# ./ubuntu18to20 --monitor
- Alternatively the status can be tracked by checking the log file at /etc/motd. Once the process completes the following message will be observed:
  
  CONFIG_TEXT: Message from the Plesk ubuntu18to20 tool:
  The server has been upgraded to Ubuntu 20.
  You can remove this message from the /etc/motd file.

Note: If the process was interrupted before the first reboot, restart it with ./ubuntu18to20 --resume option. If the interruption was after the first reboot, restart the process running systemctl restart plesk-dist-upgrader.

Note: If the operation fails before the distupgrade performs during the conversion stage, run ./ubuntu18to20 --revert to restore Plesk to normal operation. The tool will attempt to undo some of the changes it made and restart Plesk services. Once the root cause of the failure be solved try the conversion again.

Warning: Revert cannot be used to undo the changes after the distupgrade take place because packages provided by Ubuntu 20 already installed. Check the status of the conversion process and monitor its progress

Dist-upgrade from Ubuntu 18 (Bionic Beaver) to Ubuntu 20 (Focal Fossa) - Manual step by step process

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

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.
Remote management module must be installed on the server (This is because, in some tests, sshd service could not be started during the process)
Connect and perform the process connected as root or by using the # su - or # sudo su -command.
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
Temporary install msmtp component instead of Postfix. It can be done through Plesk installer or by using the command:

# plesk installer add --components msmtp

Note: this action will remove Postfix, Dovecot, SpamAssassin and Mailman components
In case the extension “TuxCare Extended Lifecycle Support” is installed, this needs to be removed with:

# plesk bin extension -u tuxcare-els
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.
Restart the DB server to apply changes:

# systemctl restart mariadb || systemctl restart mysql || systemctl restart mysqld
Make sure that update-manager-core package is installed:

# apt-get install update-manager-core
Update the current system to the latest available version:

# apt-get update && apt-get upgrade
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
Stop grafana service:

# systemctl stop grafana-server.service

Performing the dist-upgrade
Update the file sources.list 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 http://autoinstall.plesk.com/grafana/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
Update the repositories:

# apt-get update
Upgrade the kernel:

# apt-get install linux-generic
Update MariaDB to the next major version provided by the vendor:

Note: In case that the server already runs a higher version of MariaDB than 10.3 or MySQL than 5.7, skip this step.

# 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

Warning: MariaDB/MySQL will not start until the next reboot is performed.
In the mariadb config file /etc/mysql/mariadb.conf.d/50-server.cnf remove 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.
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:

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

From:

ExecReload=udevadm control --reload --timeout 0

To:

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

18.2. Then execute the following command:

# apt-get -f install
Install Systemd package:

# apt-get install systemd
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
Remove packages that were installed by dependencies and not needed anymore and LXD:

# apt-get autoremove
# apt purge lxd lxd-client
Upgrade packages:

# apt-get upgrade

Note: When prompted, you should keep the previous version of Spamassassin configuration file.
Remove packages that were installed by dependencies and not needed anymore:

# apt-get autoremove
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)
Remove packages that were installed by dependencies and not needed anymore:

# apt-get autoremove
Update Plesk to the next available version finishing the dist-upgrade process:

# plesk installer update
Fix the Bind DNS server defaults file:

# cp /etc/default/bind9 /etc/default/named
Check that all Plesk components(Dovecot, SpamAssassin, Mailman) are installed as needed. e.g. In case there were components uninstalled at 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
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server:

# shutdown -r now
Check that Plesk and all its services are working.

Dist-upgrade from Ubuntu 16 (Xenial Xerus) to Ubuntu 18 (Bionic Beaver)

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

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.
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)
Update the current system to the latest available versions:

# apt-get update && apt-get upgrade
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.
Restart the DB server to apply changes:

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

Warning: If removal of packages in the following two steps stops with message E: Unable to locate package package-name, remove the package-name from the command and run it again.
Remove packages that are no longer supported:

# apt-get remove samba-common samba-libs samba-vfs-modules
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
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-archives.plesk.com/PSA_18.0.37/ bionic all
deb http://autoinstall-archives.plesk.com/PHP70_17/ bionic all
deb http://autoinstall-archives.plesk.com/PHP71_17/ bionic all
deb http://autoinstall-archives.plesk.com/PHP72_17/ bionic all
deb http://autoinstall-archives.plesk.com/PHP73_17/ bionic all
deb http://autoinstall-archives.plesk.com/PHP74_17/ bionic all
deb http://autoinstall-archives.plesk.com/SITEBUILDER_17.8.12/ all all
deb [arch=amd64] http://autoinstall.plesk.com/PMM_0.1.11/ all all
deb [arch=amd64] http://autoinstall.plesk.com/NODE_0.0.2/ all all
deb http://autoinstall.plesk.com/grafana/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
Update the repositories:

# apt-get update
Upgrade the kernel:

# apt-get install linux-generic
Remove the string innodb_fast_shutdown=0 in the [mysqld] section, added in step 4. of section "Preparing server for upgrade" above.
Reboot the server

# reboot
Install packages dpkg and apt

# apt-get install dpkg apt
Upgrade all possible packages:

# apt-get upgrade
When prompted, choose to keep local version config installed for:
- /opt/psa/etc/apparmor.d/usr.lib.dovecot.dovecot-lda
- /etc/awstats/awstats.conf
Execute the dist-upgrade process:

# apt-get dist-upgrade
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
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-*
It is safe to install the maintainer's version for the configuration files below when prompted:
- /etc/apparmor.d/*
- /etc/ssh/sshd_config
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server.

# reboot
Check that Plesk and all its services are working.

Debian distributions

Dist-upgrade from Debian 11 to Debian 12 - Automated tool process

Preparing server for upgrade: To avoid extra downtime and/or data loss, make sure to read and understand the following information before using the distupgrade tool:

Create a full server backup: Before the upgrade, make a full server backup (which includes a full backup of all the databases). It's strongly recommend to create a snapshot as a recovery point in case the conversion process fails.
Remote management module must be installed on the server, because in some tests the sshd service could not be started during the process.
Server runs the latest version of Plesk
Notify the customers about upcoming downtime. Expected downtime is 20-30 minutes where server reboot one or more times (Plesk services, hosted websites, and emails will be unavailable).
Requirements: grub boot is installed, server has at least 5 GB of free disk space and at least 2 GB of installed RAM.
Read the list of Known issues or limiters for the tool here.
Once downloaded check the general stages of the tool with ./debian11to12 --help and the detailed plan with ./debian11to12 --show-plan output. More information can be found here.

Using the tool to upgrade from Debian 11 to Debian 12:

Connect to the server via SSH as root or other sudoer user and run sudo su -.
Download and extract the latest tool version into the server:

# wget https://github.com/plesk/debian11to12/releases/download/v1.0.0/debian11to12-1.0.0.zip
# unzip debian11to12-1.0.0.zip
# chmod 755 debian11to12
In order to monitor the conversion process, we recommend using the 'screen' utility to run the tool in the background with the following command:

# screen -S debian11to12

3.1 Run the dist upgrade convert stage by running the tool with the next command. Note that this process may reboot the server a several times:

# ./debian11to12

Note: In case the SSH connection to the server is lost, reconnect to the screen session by running screen -r debian11to12
Reconnect to the server after the above stage completes (around 20-30 minutes) and monitor the status with:

# ./debian11to12 --status

or

# ./debian11to12 --monitor
- Alternatively the status can be tracked by checking the log file at /var/log/plesk/debian11to12.log. Once the process completes the following message will be observed:
  
  CONFIG_TEXT: Message from the Plesk debian11to12 tool:
  The server has been upgraded to Debian 12.
  You can remove this message from the /etc/motd file.

Note: If the process was interrupted before the first reboot, restart it with ./debian11to12 --resume option. If the interruption was after the first reboot, restart the process running systemctl restart plesk-dist-upgrader.

Note: If the operation fails before the distupgrade performs during the conversion stage, run ./debian11to12 --revert to restore Plesk to normal operation. The tool will attempt to undo some of the changes it made and restart Plesk services. Once the root cause of the failure be solved try the conversion again.

Warning: Revert cannot be used to undo the changes after the distupgrade take place because packages provided by Debian 12 already installed. Check the status of the conversion process and monitor its progress

Dist-upgrade from Debian 11 to Debian 12 - Manual step by step process

Warning: The dist-upgrade from Debian 11 to Debian 12 is supported by Plesk Obsidian 18.0.57 version.

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

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.
Connect to the server and perform the process connected as root or by using the # su - or # sudo su -command.
Uninstall unsupported components like PHP handlers below version 7.3:

Note: before applying the command below, switch the existing websites to PHP version 7.4 or higher.

# plesk installer remove --components php7.1 php7.2 php7.3
Remove packages which were installed by dependencies but aren't required:

# apt-get autoremove
Execute the command below to be sure that system is up-to-date:

# plesk sbin pum --update

OR

# apt-get update && apt-get upgrade
Run the command to make Plesk up-to-date:

# plesk installer update
Install aptitude:

# apt-get install aptitude
Remove repository lists that are related to Plesk:

# rm -f /etc/apt/sources.list.d/plesk*.list
Replace bullseye sources lists with bookworm ones in /etc/apt/sources.list and /etc/apt/sources.list.d/*.list:

Note: below is the example for /etc/apt/sources.list file:

deb http://deb.debian.org/debian bookworm main contrib non-free
deb-src http://deb.debian.org/debian bookworm main contrib non-free

deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free
deb-src http://deb.debian.org/debian-security/ bookworm-security main contrib non-free

deb http://deb.debian.org/debian bookworm-updates main contrib non-free
deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free
Make installer to create Plesk sources list for Debian 12:

# plesk installer --override-os-version 12 --check-updates --skip-cleanup
Change bind-address in the /etc/mysql/my.cnf to accept IPv4 connections (From 10.6.0 :: refers to IPv6 strictly):

bind-address = ::ffff:127.0.0.1

To:

bind-address = 127.0.0.1
Add string below into the /etc/mysql/my.cnf file under [mysqld] section:

innodb_fast_shutdown=0
Restart MariaDB service to apply the changes:

# systemctl restart mariadb

Install modern kernel, libc6, python3, mariadb packages with the command:

Note: In case that the server already runs a higher version of MariaDB e.g. 10.6, remove mariadb-server-10.5 from the below command before run.

# aptitude install base-files linux-image-amd64 libc6 python3 mariadb-server-10.5

Note:Make sure that after execution of the command above, Plesk-related packages are not marked, for removal, normally list should be as below:

Remove the following packages:
1 python3-debianbts [3.1.0 (now)]
2 python3-pycurl [7.43.0.6-5 (now)]
3 python3-pysimplesoap [1.16.2-3 (now)]
4 python3-reportbug [7.10.3+deb11u1 (now)]
5 reportbug [7.10.3+deb11u1 (now)]

Note: when you will be asking to overwrite sshd configuration, left it as is. Also allow automatic restart for services

Remove line below from the /etc/mysql/my.cnf file:

innodb_fast_shutdown=0
Reboot the server
Execute the command below to get Plesk build for Debian 12 OS:

# plesk installer update --skip-cleanup
Update the Plesk extensions:

# plesk bin extension -l | egrep '(panel-migrator|site-import|docker|grafana|ruby)' | awk {'print $1'} | xargs -i plesk bin extension -i {}
Complete distupgrade process:

# apt-get dist-upgrade

Note: leave configuration for Postfix, PAM, rsyslog, SpamAssassin, cloud-init and other services as is.
Optional step: Remove unused packages:

# apt-get autoremove
Optional step: Purge the configuration files of the removed packages:

# apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`
Restore the Plesk packages configuration:

# plesk installer update
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server

Dist-upgrade from Debian 10 to Debian 11

Warning: The dist-upgrade from Debian 10 to Debian 11 is supported by Plesk Obsidian 18.0.42 version.

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

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.
Connect to the server and perform the process connected as root or by using the # su - or # sudo su -command.
Uninstall unsupported components like mailman, webalizer, watchdog and PHP handlers below version 7.3:

Note: before applying the command below, switch the existing websites to PHP version 7.4 or higher.

# plesk installer remove --components php7.1 php7.2 php7.3 mailman webalizer watchdog
Remove packages which were installed by dependencies but aren't required:

# apt-get autoremove
Execute the command below to be sure that system is up-to-date:

# plesk sbin pum --update

OR

# apt-get update && apt-get upgrade
Run the command to make Plesk up-to-date:

# plesk installer update
Install aptitude:

# apt-get install aptitude
Remove repository lists that are related to Plesk:

# rm -f /etc/apt/sources.list.d/plesk*.list
Replace buster sources lists with bullseye ones in /etc/apt/sources.list and /etc/apt/sources.list.d/*.list:

Note: below is the example for /etc/apt/sources.list file:

CONFIG_TEXT: deb http://deb.debian.org/debian bullseye main contrib non-free
deb-src http://deb.debian.org/debian bullseye main contrib non-free

deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-free
deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib non-free

deb http://deb.debian.org/debian bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free
Make installer to create Plesk sources list for Debian 11:

# plesk installer --override-os-version 11 --check-updates --skip-cleanup
Add string below into the /etc/mysql/my.cnf file under [mysqld] section:

CONFIG_TEXT: innodb_fast_shutdown=0
Restart MariaDB service to apply the changes:

# systemctl restart mariadb
Install modern kernel, libc6, python3, mariadb packages with the command:

Note: In case that the server already runs a higher version of MariaDB e.g. 10.6, remove mariadb-server-10.5 from the below command before run.

# aptitude install base-files linux-image-amd64 libc6 python3 mariadb-server-10.5

Note:Make sure that after execution of the command above, Plesk-related packages are not marked, for removal, normally list should be as below:

CONFIG_TEXT: Remove the following packages:
1. g++-8 [8.3.0-6 (now)] \
2. galera-3 [25.3.25-2 (now)] \
3. gcc-8 [8.3.0-6 (now)] \
4. libgcc-8-dev [8.3.0-6 (now)] \
5. libpython-stdlib [2.7.16-1 (now)] \
6. libstdc++-8-dev [8.3.0-6 (now)] \
7. mariadb-client-10.3 [1:10.3.22-0+deb10u1 (now)] \
8. mariadb-client-core-10.3 [1:10.3.22-0+deb10u1 (now)] \
9. mariadb-server-10.3 [1:10.3.22-0+deb10u1 (now)] \
10. mariadb-server-core-10.3 [1:10.3.22-0+deb10u1 (now)] \
11. openssh-sftp-server [1:7.9p1-10+deb10u1 (now)] \
12. python [2.7.16-1 (now)] \
13. python-minimal [2.7.16-1 (now)]
Note: when you will be asking to overwrite sshd configuration, left it as is. Also allow automatic restart for services
Remove line below from the /etc/mysql/my.cnf file:

CONFIG_TEXT: innodb_fast_shutdown=0
Reboot the server
Rename configuration from bind9 to named:

# mv /etc/default/bind9 /etc/default/named
Execute the command below to get Plesk build for Debian 11 OS:

# plesk installer update --skip-cleanup
Update the Plesk extensions:

# plesk bin extension -l | egrep '(panel-migrator|site-import|docker|grafana|ruby)' | awk {'print $1'} | xargs -i plesk bin extension -i {}
Complete distupgrade process:

# apt-get dist-upgrade

Note: leave configuration for Postfix, PAM, rsyslog, SpamAssassin, cloud-init and other services as is.
Optional step: Remove unused packages:

# apt-get autoremove
Optional step: Purge the configuration files of the removed packages:

# apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`
Restore the Plesk packages configuration:

# plesk installer update
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server

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.

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.
Connect and perform the process connected as root or by using the # su - or # sudo su -command.
Uninstall unsupported components such as Docker and PHP below version 7.0 with Plesk installer.

Note: More information can be found here: Software Requirements for Plesk Obsidian
Temporary install msmtp component instead of Postfix. It can be done through Plesk installer or by using the command:

# plesk installer add --components msmtp --source http://autoinstall-archives.plesk.com
Add to the mariadb/mysql config file (Usually /etc/mysql/my.cnf) the string innodb_fast_shutdown=0 in the [mysqld] section.
Restart the DB server to apply changes:

# systemctl stop mariadb.service ; systemctl start mariadb.service
Update the current system to the latest available versions:

# apt-get update && apt-get upgrade
Remove all plesk-related repos from /etc/apt/sources.list.d/. For example, you can archive them by using the next command:

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

# systemctl stop grafana-server.service
Replace stretch sources lists with buster ones in /etc/apt/sources.list and /etc/apt/sources.list.d/*.list:

Note: below is the example for the resulting /etc/apt/sources.list file:

# 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
Make installer to create Plesk sources list for Debian 10:

# plesk installer --override-os-version 10.0 --check-updates --skip-cleanup --source http://autoinstall-archives.plesk.com
Temporarily add the following Plesk repositories (e.g. vi /etc/apt/sources.list.d/plesk_temp.list):

CONFIG_TEXT: deb https://autoinstall-archives.plesk.com/pool/PSA_18.0.44_9078/ buster all
deb https://autoinstall-archives.plesk.com/SITEBUILDER_18.0.29 all all
deb https://autoinstall-archives.plesk.com/PHP80_17 buster all
deb https://autoinstall-archives.plesk.com/PHP81_17 buster all
deb https://autoinstall-archives.plesk.com/PHP74_17 buster all
deb https://autoinstall-archives.plesk.com/PHP73_17 buster all
deb https://autoinstall-archives.plesk.com/PHP72_17 buster all
deb https://autoinstall-archives.plesk.com/PHP71_17 buster all
Run apt update to refresh the repositories:

# apt update
Run the dist-upgrade to upgrade the packages from Debian 9 to Debian

# apt dist-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.
Remove the temporary sources file created in step 12 (e.g. rm /etc/apt/sources.list.d/plesk_temp.list).
Run plesk installer to update the current packages:

# plesk installer update --source http://autoinstall-archives.plesk.com
In case that systemctl status apache2 results in apache service being stopped/failed:

Resolve it by installing a the package and starting apache2:

# apt-get install libapache2-mod-fcgid-psa

# service apache2 start
Run apt update again:

# apt update
Update MariaDB to the next major version provided by the vendor:

Note: In case that the server already runs a higher version of MariaDB than 10.3, skip this step.

# apt-get install mariadb-server-10.3

Warning: MariaDB/MySQL may not start till the reboot is performed.
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.
When AppArmor was installed, bind service fails to start with permission denied shown at systemctl status bind9 output:

Resolve it by either disabling AppArmor with following commands or reconfigure AppArmor:

# systemctl stop apparmor
# systemctl restart bind9
Reboot the server to the new kernel:

# shutdown -r now
Clean packages installed by dependencies and not needed anymore:

# apt-get autoremove
In case AppApmor is enabled adjust it by following this article to let Bind9 load properly

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

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
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Check that Plesk and all its services are working.
Use the following commands to regenerate web server as well as DNS configuration files if needed:

# plesk repair web

# plesk repair dns

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 (Trusty Tahr) to Ubuntu 16 (Xenial Xerus)

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

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: if PHP by OS vendor was updated from third-party sources prior to dist-upgrade, it may break webmail functionality.

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.
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 .
During the script execution, you will be asked to reboot the server. Reboot the server.
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

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.
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`
Download the distupgrade scripts

# wget https://raw.githubusercontent.com/plesk/kb-scripts/master/distupgrade-helper-deb8-deb9/distupgrade.helper.deb8-deb9_pre.x64.sh

# wget https://raw.githubusercontent.com/plesk/kb-scripts/master/distupgrade-helper-deb8-deb9/distupgrade.helper.deb8-deb9.x64.sh
Move the scripts to /opt/psa/bin/

# mv distupgrade.helper.deb8-deb9*.x64.sh /opt/psa/bin/
Make the scripts executable by running following command:

# chmod +x /opt/psa/bin/distupgrade.helper.deb8-deb9*.x64.sh
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

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
Update information about system packages:

# apt-get update
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

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.
Run the repair command below to run all needed upgrade scripts:

# plesk repair installation
Reboot the server.
Check that Plesk and all its services are working.

Comments

16 comments

Ehud Ziegelman April 23, 2023 23:23

Hi Gabriel Aznarez,

Please note, that I have run the update to Ubuntu 22.04 on linux, for a second time after I already had it, in order to fully update the server, and that fully broke the server mySql (even level 4/6 of restart mySql didn't work).

I saw a Plesk KB article regarding such a problem on a Windows based server, however it occurs also on Linux based one. Possibly PHP version is related to the issue.

I had to restore an AWS snapshot.

# plesk -v
Product version: Plesk Obsidian 18.0.51.1
     OS version: Ubuntu 22.04 x86_64
     Build date: 2023/04/04 10:00
       Revision: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy


# mysql -V
mysql  Ver 8.0.32-0ubuntu0.22.04.2 for Linux on x86_64 ((Ubuntu))

# php -v
PHP 8.2.4 (cli) (built: Mar 16 2023 14:34:48) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.4, Copyright (c) Zend Technologies
    with Zend OPcache v8.2.4, Copyright (c), by Zend Technologies

# apache2 -v
Server version: Apache/2.4.56 (Ubuntu)
Server built:   2023-03-09T07:34:31

# nginx -v
nginx version: nginx/1.20.2

# hostnamectl
 Static hostname: example.com
       Icon name: computer-vm
         Chassis: vm
      Machine ID: xxxxxxxxxxxxxxxxxxxxx
         Boot ID: xxxxxxxxxxxxxxxxxxxxx
  Virtualization: xen
Operating System: Ubuntu 22.04.2 LTS
          Kernel: Linux 5.19.0-1022-aws
    Architecture: x86-64
 Hardware Vendor: Xen
  Hardware Model: HVM domU


# uname -r
5.19.0-1022-aws

# uname -mrs
Linux 5.19.0-1022-aws x86_64

AWS
8 GB RAM, 2 vCPUs, 160 GB SSD

Ehud Ziegelman April 24, 2023 23:17
Hi Gabriel Aznarez,

I'm pretty sure, the adaptation of step regarding mySql appearing for Ubuntu 18.04 upgrade to version 20.04, are missing on the guidance for upgrade from version 20.04 to version 22.04, possibly leading to server failure.

Can you please give your take?
1. 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
  
  Warning: MariaDB/MySQL will not start until the next reboot is performed.
2. In the mariadb config file /etc/mysql/mariadb.conf.d/50-server.cnf remove 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.
3. 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:
  
  At line 26 in the /lib/systemd/system/systemd-udevd.service file, the following string should be changed:
  
  From:
  
  ExecReload=udevadm control --reload --timeout 0
  
  To:
  
  ExecReload=/bin/udevadm control --reload --timeout 0
  
  And execute the following command:
  
  # apt-get -f install
0
Gabriel Aznarez April 25, 2023 16:36

Hi Ehud Ziegelman,

Thank you for your comment.

Note that the processes for each version may differ, I have just tried myself the Dist Upgrade from Ubuntu 20 to Ubuntu 22 using the steps from this article and had no issue with the process as currently is. The upgrade succeeded and Plesk as well as the sites continue to operate correctly.

Mind that as mentioned on the article suggested actions, if a process is in doubt it is recommended to first try this on a testing environment before applying it to the production one.

Feel free to share the results if you encounter any issues yourself.

Sincerely.

0
Artur J August 08, 2023 11:13 (Edited August 08, 2023 11:23)

Hello,

In my case Dist-upgrade from Debian 10 to Debian 11 take +/- 2h. I go step by step with instruction from Plesk and everything goes well. After all steps, final reboot, I meet only one inconvenience - that firewall (Fail2Ban) ban my IP due to too many connection attempts to mail service made by my phone that was on the same network. On root level everything was fine, and to figure it out it take me like 30 min :) so ... maybe one advice before start upgrading is to whitelist your current IP.

Regards

1
Fle Fle December 17, 2023 14:38

Could anyone help me with the following:
- updated everything, removed Watchdog also via suggested command
- after running : $ ./ubuntu18to20 --start

Required pre-conversion condition checking if Plesk watchdog extension is not installed not met:
The Plesk Watchdog extension is installed. Unfortunately the extension is unsupported on Ubuntu 20 and later.
Please remove the extension be calling: plesk installer remove --components watchdog

Any idea how to remove the "watchdog" entry? Is this the issue or maybe another issue?

0
hifer December 30, 2023 23:06

When upgrading from Ubuntu 18.04 to 20.04, I had issues restarting mysql service as I had "NO_AUTO_CREATE_USER" parameter in /etc/mysql/my.cnf file. Make sure you remove this as it's no longer supported in mysql 8.0.

0
hifer December 31, 2023 00:09

Note when upgrading from Ubuntu 20.04 to 22.04 and if you are using MySQL, you may get an error restarting the mySQL DB with the following error message:

[ERROR] [MY-010187] [Server] Could not open file '/var/log/mysql/error.log' for error logging: No such file or >

You can workaround this by running the following:

sudo mkdir /var/log/mysql (if the mysql folder doesn't exist)
sudo touch /var/log/mysql/error.log
sudo chown mysql:mysql /var/log/mysql/error.log
sudo chcon system_u:object_r:mysqld_log_t:s0 /var/log/mysql/error.log

0
Florian Cheno February 21, 2024 08:40

Hello,

the following line appaears in the manual update process:

"aptitude install base-files linux-image-amd64 libc6 python3 mariadb-server-10.5"

But Debian 12 provides MariaDB 10.11. Is this an error?

1
Stephanie Kerchof August 14, 2024 11:16 (Edited August 14, 2024 11:17)

Hello,

I just went through the manual upgrade from Debian 11 to Debian 12. I would like to mention that there are steps missing related to mariadb. Mariadb 10.5 is not supported in Debian 12. It needs to be upgraded to an newer version. Here is what I did:

After step 14 (giving warning related to mariadb 10.5), I edited panel.ini using plesk conf panel.ini command to add the following lines:

[databaseManagement]
features.canBeUpgraded = 1

I wen to plesk web UI and ask for an automatic upgrade of the mariadb packages (Tools & Settings -> Database Servers).

Then I continued the procedure.

0
Guido Bender August 17, 2024 23:13 (Edited August 18, 2024 00:48)

Be careful. Plesk encouraged us to upgrade to MariaDB 10.11 previous Debian 11. I was on Debian 10 doing this:
https://support.plesk.com/hc/en-us/articles/12388091703703-How-to-upgrade-MySQL-5-5-to-5-6-5-7-or-MariaDB-5-5-to-10-x-on-Linux

Now this dist-upgrade broke my installation because of step 13
aptitude install mariadb-server-10.5
I got a new folder /var/lib/mysql and my old database in /var/lib/mysql-10.11

It took me a long time to get the dist-upgrade complete while repairing the database, but in the end this could do the upgrade on the tables again:
https://support.plesk.com/hc/en-us/articles/12388091703703-How-to-upgrade-MySQL-5-5-to-5-6-5-7-or-MariaDB-5-5-to-10-x-on-Linux

After upgrading by that instruction from 10.5 to 10.11 the tables were "in engine" again and fully working.

1
WNC Cloud November 26, 2024 01:05

When I get to step 14 on trying to upgrade from 22.04 to 24.04, I get the following:

root@plesk1:/home/wnccloud# aptitude install base-files linux-generic libc6 python3 mariadb-server
The following NEW packages will be installed:
gcc-14-base{a} linux-image-6.8.0-49-generic{a} linux-modules-6.8.0-49-generic{a} linux-modules-extra-6.8.0-49-generic{a}
mariadb-plugin-provider-bzip2{a} mariadb-plugin-provider-lz4{a} mariadb-plugin-provider-lzma{a} mariadb-plugin-provider-lzo{a}
mariadb-plugin-provider-snappy{a} pv{a} python3-cssselect{a} ubuntu-kernel-accessories{a}
The following packages will be REMOVED:
libnsl-dev{u} libpython3-stdlib{u} libtirpc-dev{u} linux-headers-generic{u} mariadb-server-10.6{a} python3-distutils{a} python3-lib2to3{u}
python3-minimal{u}
The following packages will be upgraded:
base-files libc-bin libc-dev-bin libc6 libc6-dev libnewt0.52 libsnappy1v5 libstdc++6 linux-generic{b} linux-image-generic locales locales-all
mariadb-common mariadb-server{b} python3{b} python3-cffi-backend python3-lxml python3-markupsafe python3-netifaces python3-newt
python3-pyrsistent python3-systemd python3-yaml python3-zope.interface
The following packages are RECOMMENDED but will NOT be installed:
libc-devtools libc-devtools:i386 manpages-dev
24 packages upgraded, 12 newly installed, 8 to remove and 792 not upgraded.
Need to get 195 MB of archives. After unpacking 157 MB will be used.
The following packages have unmet dependencies:
python3-gi : Depends: python3 (< 3.11) but 3.12.3-0ubuntu2 is to be installed
mariadb-server : Depends: mariadb-client (>= 1:10.11.8-0ubuntu0.24.04.1) but it is not going to be installed
Depends: mariadb-server-core (>= 1:10.11.8-0ubuntu0.24.04.1) but it is not going to be installed
Depends: libssl3t64 (>= 3.0.0) but it is not going to be installed
python3 : PreDepends: python3-minimal (= 3.12.3-0ubuntu2) but it is not going to be installed
   Depends: python3.12 (>= 3.12.3-0~) but it is not installable
   Depends: libpython3-stdlib (= 3.12.3-0ubuntu2) but it is not going to be installed
plesk-service-node-utilities : Depends: python3-distutils but it is not going to be installed
linux-generic : Depends: linux-headers-generic (= 6.8.0-49.49) but it is not going to be installed
python3-wheel : Depends: python3-distutils but it is not going to be installed
python3-gdbm : Depends: python3 (< 3.12) but 3.12.3-0ubuntu2 is to be installed
plesk-core-utilities : Depends: python3-distutils but it is not going to be installed
python3-apt : Depends: python3 (< 3.11) but 3.12.3-0ubuntu2 is to be installed
python3-dev : Depends: python3 (= 3.10.6-1~22.04.1) but 3.12.3-0ubuntu2 is to be installed
   Depends: python3-distutils (>= 3.10.6-1~) but it is not going to be installed
python3-pip : Depends: python3-distutils but it is not going to be installed
python3-setuptools : Depends: python3-distutils but it is not going to be installed
python3-dbus : Depends: python3 (< 3.11) but 3.12.3-0ubuntu2 is to be installed
shim-signed : Depends: grub-efi-amd64-signed (>= 1.191~) but 1.187.6+2.06-2ubuntu14.4 is installed and it is kept back or
grub-efi-arm64-signed (>= 1.191~) which is a virtual package and is not provided by any available package
or
base-files (< 12.3) but 13ubuntu10.1 is to be installed
open: 8722; closed: 11519; defer: 81; conflict: 91 oNo solution found within the allotted time. Try harder? [Y/n]

1
UES November 26, 2024 16:29

When the Ubuntu 22 → 24 automated upgrade will be available?

2
King555 December 28, 2024 22:04

I had an error message after running the automated 18 to 20 upgrade and I want to tell you about it, maybe someone needs this information one day.
After about 50 % of the process I got the message "Failed: upgrade GRUB from new repositories." and the upgrade stopped.
I googled it and tried "dpkg --audit" to see "half-configured" packages. There could have been a package with "grub" in the name, but instead there was a package called "cloud-init" which was the error.
When I tried to fix this package I always got "installed cloud-init package post-installation script subprocess returned error".
So I just removed the package with "apt remove --purge cloud-init" and restarted the upgrade process with "./ubuntu18to20 --resume" and now it worked.
If you need "cloud-init" you can reinstall it later (if it works then).

0
eCom Seller January 10, 2025 16:00

Will an automated installer be coming out for Ubuntu 22 to 24 migrations?

0
filmotheklown February 03, 2025 19:44

WNC Cloud Did you find a solution to this? I'm getting the exact same error.

0
Sec Hosting February 07, 2025 20:52

Hi Gabriel Aznarez ,
thanks for that How To Guide. We did tests (Ubuntu 22.04 > 24.04) about a month ago in our LAB. Today we performed upgrades in our prod environment based on Plesk Obsidian 18.0.67 Update 2 also from Ubuntu 22.04 > 24.04.
Everything worked like great and without any issues. Except one thing: during tests in our LAB we noticed that it's better to remove Grafana Extension and Monitoring Add-On. Because with both installed Step 20 failed on two LAB tests:

plesk bin extension -l | egrep '(panel-migrator|site-import|docker|grafana)'| awk {'print $1'} | xargs -i plesk bin extension -i {}

[2025-01-06 07:38:20.920] 43652:677b87840c931 ERR [extension/grafana] The execution of post-install.php has failed with the following message:

[2025-01-06 07:38:20.904] 43818:677b881dcac43 ERR [extension/grafana] Grafana service failed to start

The execution of post-install.php has failed with the following message:

[2025-01-06 07:38:20.904] 43818:677b881dcac43 ERR [extension/grafana] Grafana service failed to start

exit status 1

In our prod environment we removed both (Grafana and Monitoring extension) on all machines before we started with the steps above and with that, we didn't run into any issues on Step 20. So not any issue for us at the moment - but wanted to let you know that this happened twice in our LAB to us and what was our “workaround”. And sorry I do not have any more logs for you because this LAB environment is already destroyed.
However all machines are on Ubuntu 24.04 :)
Cheers
Norman

0

Please sign in to leave a comment.

Have more questions? Submit a request

Articles in this section

Applicable to:

How to perform a dist-upgrade?

Ubuntu distributions

Debian distributions

Unsupported EOLed OSes

Related articles