Articles in this section

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

Gabriel Aznarez
Updated
Plesk for Linux kb: technical Plesk Obsidian for Linux ABT: Group A

Note: If you’d like Plesk to assist with this task or handle it on your behalf, you can submit a request to the Plesk Professional Services team here: Plesk Professional Services – Administrative Services.

Supported versions and operating systems for dist-upgrade

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

Note: Learn how to upgrade a Plesk server from CentOS 7 to AlmaLinux 8 here.

  •  

Recommendations and limitations:

Limitations:

  • The dist-upgrade procedure cannot be performed in a containerized environment. By design, container virtualization does not include a full operating system image; instead, it relies on a shared base OS and isolates only applications and services. If you are unsure whether your server is containerized, contact your hosting provider to confirm the type of environment in use.
  • 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

Recommendations:

  • If you have never performed a dist-upgrade before, it is strongly recommended to test the upgrade on a cloned server first. Use the clone to identify and resolve potential issues and to verify that Plesk functions correctly after the upgrade before proceeding on a production system.
  • Before starting the upgrade process, consider creating: a full server snapshot, and/or a complete server backup.
Ubuntu Distributions
Dist-upgrade from Ubuntu 22 to Ubuntu 24 - Manual step by step process

Preparing server for upgrade

  1. Connect to the server via SSH

  2. Change to root user by using the following command:

    # sudo su -

  3. Remove packages which were installed by dependencies but are not required:

    # apt-get autoremove

  4. Execute the command below to be sure that system is up-to-date:

    # plesk sbin pum --update

  5. Run the command to make Plesk up-to-date:

    # plesk installer update

  6. Install aptitude:

    # apt-get install aptitude

  7. Remove repository lists that are related to Plesk:

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

    Performing the dist-upgrade

  8. 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

  9. Make installer to create Plesk sources list for Ubuntu 24.04:

    # plesk installer --override-os-version 24.04 --check-updates --skip-cleanup

  10. 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

  11. Add the string below into the /etc/mysql/my.cnf file under [mysqld] section:

    innodb_fast_shutdown=0

  12. Restart MariaDB/MySQL service to apply the changes:

    # systemctl restart mariadb || systemctl restart mysql

  13. 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

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

    innodb_fast_shutdown=0

  15. Reboot the server:

    # reboot

  16. Wait some time for the server to reboot, then connect to the server via SSH

  17. Switch to root user:

    # sudo su -

  18. Execute the command below to get Plesk build for Ubuntu 24.04:

    # plesk installer update --skip-cleanup

  19. Update the Plesk extensions:

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

  20. Complete distupgrade process:

    # apt-get dist-upgrade

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

  21. Optional step: Remove unused packages:

    # apt-get autoremove

  22. Optional step: Purge the configuration files of the removed packages:

    # apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`

  23. Restore the Plesk packages configuration:

    # plesk installer update

  24. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

  25. Reboot the server:

    # reboot

  26. Wait some time for the server to reboot and check that Plesk and all its services are working.
Dist-upgrade from Ubuntu 20 to Ubuntu 22 - 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:

  • Remote management module must be installed on the server, because in some tests the sshd service could not be started during the process.
  • Read the list of Known issues or limiters for the tool here.

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

  1. Connect to the server via SSH as root or other sudoer user and run sudo su -.

  2. Download and extract the latest tool version into the server (replace the link/file name in the commands):

    # wget https://github.com/plesk/ubuntu20to22/releases/download/v1.1.7/ubuntu20to22-1.1.7.zip
    # unzip ubuntu20to22-1.1.7.zip
    # chmod 755 ubuntu20to22

  3. 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

  4. 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 to Ubuntu 22 - Manual step by step process

Preparing server for upgrade

  1. Connect to the server via SSH

  2. Change to root user by using the following command:

    # sudo su -

  3. Enable enhanced security mode:

    # plesk bin passwords --encrypt

  4. Uninstall the unsupported component - Mailman:

    # plesk installer remove --components mailman

  5. Remove packages which were installed by dependencies but are not required:

    # apt-get autoremove

  6. Execute the command below to be sure that system is up-to-date:

    # plesk sbin pum --update

  7. Run the command to make Plesk up-to-date:

    # plesk installer update

  8. Install aptitude:

    # apt-get install aptitude

  9. Remove repository lists that are related to Plesk:

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

    Performing the dist-upgrade

  10. 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

  11. Make installer to create Plesk sources list for Ubuntu 22.04:

    # plesk installer --override-os-version 22.04 --check-updates --skip-cleanup

  12. 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

  13. Add the string below into the /etc/mysql/my.cnf file under [mysqld] section:

    innodb_fast_shutdown=0

  14. Restart MariaDB/MySQL service to apply the changes:

    # systemctl restart mariadb || systemctl restart mysql

  15. 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

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

    innodb_fast_shutdown=0

  17. Reboot the server:

    # reboot

  18. Wait some time for the server to reboot, then connect to the server via SSH

  19. Switch to root user:

    # sudo su -

  20. Execute the command below to get Plesk build for Ubuntu 22.04:

    # plesk installer update --skip-cleanup

  21. Update the Plesk extensions:

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

  22. Complete distupgrade process:

    # apt-get dist-upgrade

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

  23. Optional step: Remove unused packages:

    # apt-get autoremove

  24. Optional step: Purge the configuration files of the removed packages:

    # apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`

  25. Restore the Plesk packages configuration:

    # plesk installer update

  26. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

  27. Reboot the server:

    # reboot

  28. Wait some time for the server to reboot and check that Plesk and all its services are working.
Dist-upgrade from Ubuntu 18 to Ubuntu 20 - 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:

  • Remote management module must be installed on the server, because in some tests the sshd service could not be started during the process.
  • 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:

  1. Connect to the server via SSH as root or other sudoer user and run sudo su -.

  2. Download and extract the latest tool version into the server:

    # wget https://github.com/plesk/ubuntu18to20/releases/download/v2.2.0/ubuntu18to20-2.2.0.zip
    # unzip ubuntu18to20-2.2.0.zip
    # chmod 755 ubuntu18to20

  3. 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

  4. 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:

      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 to Ubuntu 20 - Manual step by step process

Warning: The dist-upgrade process from Ubuntu 18.04 to Ubuntu 20.04 is supported since 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. Remote management module must be installed on the server (This is because, in some tests, sshd service could not be started during the process)
  2. Connect and perform the process connected as root or by using the # su - or # sudo su -command.

  3. 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

  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

    Note: this action will remove Postfix, Dovecot, SpamAssassin and Mailman components

  5. In case the extension “TuxCare Extended Lifecycle Support” is installed, this needs to be removed with:

    # plesk bin extension -u tuxcare-els

  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 version:

    # 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

  12. 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

  13. Update the repositories:

    # apt-get update

  14. Upgrade the kernel:

    # apt-get install linux-generic

  15. 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.

  16. 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.

  17. 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

  18. Install Systemd package:

    # apt-get install systemd

  19. 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

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

    # apt-get autoremove
    # apt purge lxd lxd-client

  21. Upgrade packages:

    # apt-get upgrade

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

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

    # apt-get autoremove

  23. 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)

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

    # apt-get autoremove

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

    # plesk installer update

  26. Fix the Bind DNS server defaults file:

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

  27. 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

  28. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

  29. Reboot the server:

    # shutdown -r now

  30. Check that Plesk and all its services are working.
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. 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)

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

    # apt-get update && apt-get upgrade

  3. 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.

  4. 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.

  5. Remove packages that are no longer supported:

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

  6. 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

  7. 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

  8. Update the repositories:

    # apt-get update

  9. Upgrade the kernel:

    # apt-get install linux-generic

  10. Remove the string innodb_fast_shutdown=0 in the [mysqld] section, added in step 4. of section "Preparing server for upgrade" above.

  11. Reboot the server

    # reboot

  12. Install packages dpkg and apt

    # apt-get install dpkg apt

  13. Upgrade all possible packages:

    # apt-get upgrade

  14. When prompted, choose to keep local version config installed for:
    • /opt/psa/etc/apparmor.d/usr.lib.dovecot.dovecot-lda
    • /etc/awstats/awstats.conf

  15. Execute the dist-upgrade process:

    # apt-get dist-upgrade

  16. 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

  17. 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-*
  18. It is safe to install the maintainer's version for the configuration files below when prompted:
    • /etc/apparmor.d/*
    • /etc/ssh/sshd_config

  19. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

  20. Reboot the server.

    # reboot

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

 

Debian Distributions
Dist-upgrade from Debian 12 to Debian 13 - Information

  • As described here, Dist-upgrade from Debian 12 to Debian 13 is not yet supported by Plesk. The recommended way to switch to Debian 13 is using Plesk Migrator. Support for dist-upgrade and/or dist-upgrade CLI helper will be added later.

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:

  • Remote management module must be installed on the server, because in some tests the sshd service could not be started during the process.
  • 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:

  1. Connect to the server via SSH as root or other sudoer user and run sudo su -.

  2. Download and extract the latest tool version into the server:

    # wget https://github.com/plesk/debian11to12/releases/download/v1.0.3/debian11to12-1.0.3.zip
    # unzip debian11to12-1.0.3.zip
    # chmod 755 debian11to12

  3. 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

  4. 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:

      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 since Plesk Obsidian 18.0.57 version.

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

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

  2. 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

  3. Remove packages which were installed by dependencies but aren't required:

    # apt-get autoremove

  4. Execute the command below to be sure that system is up-to-date:

    # plesk sbin pum --update

    OR

    # apt-get update && apt-get upgrade

  5. Run the command to make Plesk up-to-date:

    # plesk installer update

  6. Install aptitude:

    # apt-get install aptitude

  7. Remove repository lists that are related to Plesk:

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

  8. 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

  9. Make installer to create Plesk sources list for Debian 12:

    # plesk installer --override-os-version 12 --check-updates --skip-cleanup

  10. 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

  11. Add string below into the /etc/mysql/my.cnf file under [mysqld] section:

    innodb_fast_shutdown=0

  12. Restart MariaDB service to apply the changes:

    # systemctl restart mariadb

  13. 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 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

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

    CONFIG_TEXT: innodb_fast_shutdown=0

  15. Reboot the server

  16. Execute the command below to get Plesk build for Debian 12 OS:

    # plesk installer update --skip-cleanup

  17. 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 {}

  18. Complete distupgrade process:

    # apt-get dist-upgrade

    **Note**: leave configuration for Postfix, PAM, rsyslog, SpamAssassin, cloud-init and other services as is.

    18.1 Optional step: Remove unused packages:

    # apt-get autoremove

    18.2 Optional step: Purge the configuration files of the removed packages:

    # apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`

  19. Restore the Plesk packages configuration:

    # plesk installer update

  20. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

  21. Reboot the server
Dist-upgrade from Debian 10 to Debian 11

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

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

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

  2. 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

  3. Remove packages which were installed by dependencies but aren't required:

    # apt-get autoremove

  4. Execute the command below to be sure that system is up-to-date:

    # plesk sbin pum --update

    OR

    # apt-get update && apt-get upgrade

  5. Run the command to make Plesk up-to-date:

    # plesk installer update

  6. Install aptitude:

    # apt-get install aptitude

  7. Remove repository lists that are related to Plesk:

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

  8. 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

  9. Make installer to create Plesk sources list for Debian 11:

    # plesk installer --override-os-version 11 --check-updates --skip-cleanup

  10. Add string below into the /etc/mysql/my.cnf file under [mysqld] section:

    CONFIG_TEXT: innodb_fast_shutdown=0

  11. Restart MariaDB service to apply the changes:

    # systemctl restart mariadb

  12. 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:
    g++-8 [8.3.0-6 (now)]
    galera-3 [25.3.25-2 (now)]
    gcc-8 [8.3.0-6 (now)]
    libgcc-8-dev [8.3.0-6 (now)]
    libpython-stdlib [2.7.16-1 (now)]
    libstdc++-8-dev [8.3.0-6 (now)]
    mariadb-client-10.3 [1:10.3.22-0+deb10u1 (now)]
    mariadb-client-core-10.3 [1:10.3.22-0+deb10u1 (now)]
    mariadb-server-10.3 [1:10.3.22-0+deb10u1 (now)]
    mariadb-server-core-10.3 [1:10.3.22-0+deb10u1 (now)]
    openssh-sftp-server [1:7.9p1-10+deb10u1 (now)]
    python [2.7.16-1 (now)]
    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

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

    CONFIG_TEXT: innodb_fast_shutdown=0

  14. Reboot the server

  15. Rename configuration from bind9 to named:

    # mv /etc/default/bind9 /etc/default/named

  16. Execute the command below to get Plesk build for Debian 11 OS:

    # plesk installer update --skip-cleanup

  17. 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 {}

  18. Complete distupgrade process:

    # apt-get dist-upgrade

    Note: leave configuration for Postfix, PAM, rsyslog, SpamAssassin, cloud-init and other services as is.

  19. Optional step: Remove unused packages:

    # apt-get autoremove

  20. Optional step: Purge the configuration files of the removed packages:

    # apt-get purge `dpkg -l | grep "^rc" | awk '{print $2}'`

  21. Restore the Plesk packages configuration:

    # plesk installer update

  22. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

  23. Reboot the server
Dist-upgrade from Debian 9 to Debian 10

Warning: dist-upgrade from Debian 9 to Debian 10 is supported since 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.

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

  2. 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

  3. 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

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

  5. Restart the DB server to apply changes:

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

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

    # apt-get update && apt-get upgrade

  7. 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

  8. Stop grafana service:

    # systemctl stop grafana-server.service

  9. 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

  10. 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

  11. Temporarily add the following Plesk repositories (e.g. vi /etc/apt/sources.list.d/plesk_temp.list):

    deb https://autoinstall-archives.plesk.com/pool/PSA_18.0.44_9078/ buster alldeb 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

  12. Run apt update to refresh the repositories:

    # apt update

  13. 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.

  14. Remove the temporary sources file created in step 12 (e.g. rm /etc/apt/sources.list.d/plesk_temp.list).

  15. Run plesk installer to update the current packages:

    # plesk installer update --source http://autoinstall-archives.plesk.com

  16. 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

  17. Run apt update again:

    # apt update

  18. 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.

  19. 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.

  20. 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

  21. Reboot the server to the new kernel:

    # shutdown -r now

  22. Clean packages installed by dependencies and not needed anymore:

    # apt-get autoremove

  23. 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-curlplesk-mail-pc-driver``postfixpsa-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

  24. 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

  25. Run the repair command below to run all needed upgrade scripts:

    # plesk repair installation

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

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

    # plesk repair web
    # plesk repair dns

Was this article helpful?

Comments

21 comments
Date Votes
  • Avatar
    Ehud Ziegelman

    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
    0
  • Avatar
    Ehud Ziegelman

    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:

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

      2. From:

        ExecReload=udevadm control --reload --timeout 0

      3. To:

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

      4. And execute the following command:

        # apt-get -f install

     

    0
  • Avatar
    Gabriel Aznarez

    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
  • Avatar
    Artur J
    (Edited )

    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
  • Avatar
    Fle Fle

    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
  • Avatar
    hifer

    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
  • Avatar
    hifer

    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
  • Avatar
    Florian Cheno

    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
  • Avatar
    Stephanie Kerchof
    (Edited )

    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
  • Avatar
    Guido Bender
    (Edited )

    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
  • Avatar
    WNC Cloud

    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
  • Avatar
    UES

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

    2
  • Avatar
    King555

    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
  • Avatar
    eCom Seller

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

    0
  • Avatar
    filmotheklown

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

    0
  • Avatar
    Sec Hosting

    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
  • Avatar
    B Pfl
    (Edited )

    Hi Gabriel Aznarez I followed the instruction for a manual upgrade from Ubuntu 20.04 to 22.04. 

    At a first glance it seems as if most things are running. Here are a few issues that I encountered: 

    • I first tried the automated update process. This seems to have failed because the Imunify extension was/is installed and the update check failed (sources were not changed to jammy). 
    • After the upgrade, systemd-timesyncd was not working (segfault). A re-install through apt made it run again (looks like some strange i386 version was installed first and did not work). Interesting fact: even though I have an amd64 installation, the upgrade process installed the following i386 packages: gcc-12-base, libc6, libcrypt1, libgcc-s1, libidn2-0, libunistring2. 
    • when running “plesk repair installation” in step 27, quite a few warning appear which make me doubt that this command works properly. In particular it seems to still assume that I am using Ubuntu 20.04 even though I have upgraded (/etc/lsb-release and plesk version correctly report 22.04). 

    WARNING: Skip fixing 'liblog4cplus': Cannot find deb-archive for package liblog4cplus (1.2.0.1-ubuntu.20.04.210430.1632)
    WARNING: Skip fixing 'plesk-libboost-1.65': Cannot find deb-archive for package plesk-libboost-1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-1.74': Cannot find deb-archive for package plesk-libboost-1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-1.79': Cannot find deb-archive for package plesk-libboost-1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-1.80': Cannot find deb-archive for package plesk-libboost-1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-1.82': Cannot find deb-archive for package plesk-libboost-1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-chrono1.65': Cannot find deb-archive for package plesk-libboost-chrono1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-chrono1.74': Cannot find deb-archive for package plesk-libboost-chrono1.74 (1.74.0.
    1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-chrono1.79': Cannot find deb-archive for package plesk-libboost-chrono1.79 (1.79.0-
    ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-chrono1.80': Cannot find deb-archive for package plesk-libboost-chrono1.80 (1.80.0-
    ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-chrono1.82': Cannot find deb-archive for package plesk-libboost-chrono1.82 (1.82.0-
    ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-date-time1.65': Cannot find deb-archive for package plesk-libboost-date-time1.65 (1
    .65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-date-time1.74': Cannot find deb-archive for package plesk-libboost-date-time1.74 (1
    .74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-date-time1.79': Cannot find deb-archive for package plesk-libboost-date-time1.79 (1
    .79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-date-time1.80': Cannot find deb-archive for package plesk-libboost-date-time1.80 (1
    .80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-date-time1.82': Cannot find deb-archive for package plesk-libboost-date-time1.82 (1
    .82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-filesystem1.65': Cannot find deb-archive for package plesk-libboost-filesystem1.65 
    (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-filesystem1.74': Cannot find deb-archive for package plesk-libboost-filesystem1.74 
    (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-filesystem1.79': Cannot find deb-archive for package plesk-libboost-filesystem1.79 
    (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-filesystem1.80': Cannot find deb-archive for package plesk-libboost-filesystem1.80 
    (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-filesystem1.82': Cannot find deb-archive for package plesk-libboost-filesystem1.82 
    (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-iostreams1.65': Cannot find deb-archive for package plesk-libboost-iostreams1.65 (1
    .65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-iostreams1.74': Cannot find deb-archive for package plesk-libboost-iostreams1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-iostreams1.79': Cannot find deb-archive for package plesk-libboost-iostreams1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-iostreams1.80': Cannot find deb-archive for package plesk-libboost-iostreams1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-iostreams1.82': Cannot find deb-archive for package plesk-libboost-iostreams1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-locale1.65': Cannot find deb-archive for package plesk-libboost-locale1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-locale1.74': Cannot find deb-archive for package plesk-libboost-locale1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-locale1.79': Cannot find deb-archive for package plesk-libboost-locale1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-locale1.80': Cannot find deb-archive for package plesk-libboost-locale1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-locale1.82': Cannot find deb-archive for package plesk-libboost-locale1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-program-options1.65': Cannot find deb-archive for package plesk-libboost-program-options1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-program-options1.74': Cannot find deb-archive for package plesk-libboost-program-options1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-program-options1.79': Cannot find deb-archive for package plesk-libboost-program-options1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-program-options1.80': Cannot find deb-archive for package plesk-libboost-program-options1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-program-options1.82': Cannot find deb-archive for package plesk-libboost-program-options1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-regex1.65': Cannot find deb-archive for package plesk-libboost-regex1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-regex1.74': Cannot find deb-archive for package plesk-libboost-regex1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-regex1.79': Cannot find deb-archive for package plesk-libboost-regex1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-regex1.80': Cannot find deb-archive for package plesk-libboost-regex1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-regex1.82': Cannot find deb-archive for package plesk-libboost-regex1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-serialization1.65': Cannot find deb-archive for package plesk-libboost-serialization1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-serialization1.74': Cannot find deb-archive for package plesk-libboost-serialization1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-serialization1.79': Cannot find deb-archive for package plesk-libboost-serialization1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-serialization1.80': Cannot find deb-archive for package plesk-libboost-serializatio
    n1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-serialization1.82': Cannot find deb-archive for package plesk-libboost-serializatio
    n1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-system1.65': Cannot find deb-archive for package plesk-libboost-system1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-system1.74': Cannot find deb-archive for package plesk-libboost-system1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-system1.79': Cannot find deb-archive for package plesk-libboost-system1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-system1.80': Cannot find deb-archive for package plesk-libboost-system1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-system1.82': Cannot find deb-archive for package plesk-libboost-system1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libboost-thread1.65': Cannot find deb-archive for package plesk-libboost-thread1.65 (1.65.1-ubuntu.20.04.200630.1129)
    WARNING: Skip fixing 'plesk-libboost-thread1.74': Cannot find deb-archive for package plesk-libboost-thread1.74 (1.74.0.1-ubuntu.20.04.211202.1442)
    WARNING: Skip fixing 'plesk-libboost-thread1.79': Cannot find deb-archive for package plesk-libboost-thread1.79 (1.79.0-ubuntu.20.04.220603.0338)
    WARNING: Skip fixing 'plesk-libboost-thread1.80': Cannot find deb-archive for package plesk-libboost-thread1.80 (1.80.0-ubuntu.20.04.220905.1058)
    WARNING: Skip fixing 'plesk-libboost-thread1.82': Cannot find deb-archive for package plesk-libboost-thread1.82 (1.82.0-ubuntu.20.04.230425.0643)
    WARNING: Skip fixing 'plesk-libmariadbclient-3.1': Cannot find deb-archive for package plesk-libmariadbclient-3.1 (3.1.8-ubuntu.20.04.200703.1433)
    WARNING: Skip fixing 'plesk-libmariadbclient-3.3': Cannot find deb-archive for package plesk-libmariadbclient-3.3 (3.3.10-v.ubuntu.20.04+p18.0.63.0+t240726.0752)
    WARNING: Skip fixing 'plesk-libpoco-1.9.0': Cannot find deb-archive for package plesk-libpoco-1.9.0 (1.9.0-ubuntu.20.04.200703.1727)
    WARNING: Skip fixing 'plesk-libstdc++10.3.0': Cannot find deb-archive for package plesk-libstdc++10.3.0 (10.3.0-ubuntu.20.04.210915.1419)
    WARNING: Skip fixing 'plesk-libstdc++12.2.0': Cannot find deb-archive for package plesk-libstdc++12.2.0 (12.2.0-ubuntu.20.04.230912.1305)
    WARNING: Skip fixing 'plesk-libstdc++6.3.0': Cannot find deb-archive for package plesk-libstdc++6.3.0 (6.3.0-ubuntu.20.04.200630.1040)
    WARNING: Skip fixing 'plesk-milter': Cannot find deb-archive for package plesk-milter (8.14.5-ubuntu.20.04.200703.1243)
    WARNING: Skip fixing 'plesk-nodejs10': Cannot find deb-archive for package plesk-nodejs10 (10.16.0-19102813)
    WARNING: Skip fixing 'plesk-nodejs12': Cannot find deb-archive for package plesk-nodejs12 (12.4.0-19102813)
    WARNING: Skip fixing 'plesk-nodejs8': Cannot find deb-archive for package plesk-nodejs8 (8.16.0-19102813)
    WARNING: Skip fixing 'plesk-php71-dev': Unable to fetch deb-archive for package plesk-php71-dev (7.1.33-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php71-dev=7.1.33-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72': Unable to fetch deb-archive for package plesk-php72 (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-bcmath': Unable to fetch deb-archive for package plesk-php72-bcmath (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-bcmath=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-cli': Unable to fetch deb-archive for package plesk-php72-cli (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-cli=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-dba': Unable to fetch deb-archive for package plesk-php72-dba (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y p
    lesk-php72-dba=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-dev': Unable to fetch deb-archive for package plesk-php72-dev (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-dev=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-enchant': Unable to fetch deb-archive for package plesk-php72-enchant (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-enchant=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-fpm': Unable to fetch deb-archive for package plesk-php72-fpm (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-fpm=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-gd': Unable to fetch deb-archive for package plesk-php72-gd (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-gd=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-imagick': Unable to fetch deb-archive for package plesk-php72-imagick (3.4.4-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-imagick=3.4.4-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-imap': Unable to fetch deb-archive for package plesk-php72-imap (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-imap=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-intl': Unable to fetch deb-archive for package plesk-php72-intl (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-intl=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-ioncube-loader': Unable to fetch deb-archive for package plesk-php72-ioncube-loader (10.4.5-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-ioncube-loader=10.4.5-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-ldap': Unable to fetch deb-archive for package plesk-php72-ldap (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-ldap=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-mbstring': Unable to fetch deb-archive for package plesk-php72-mbstring (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-mbstring=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-mysql': Unable to fetch deb-archive for package plesk-php72-mysql (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-mysql=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-odbc': Unable to fetch deb-archive for package plesk-php72-odbc (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-odbc=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-opcache': Unable to fetch deb-archive for package plesk-php72-opcache (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-opcache=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-pdo': Unable to fetch deb-archive for package plesk-php72-pdo (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-pdo=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-pear': Unable to fetch deb-archive for package plesk-php72-pear (1.10.12-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-pear=1.10.12-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-pgsql': Unable to fetch deb-archive for package plesk-php72-pgsql (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-pgsql=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-process': Unable to fetch deb-archive for package plesk-php72-process (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-process=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-pspell': Unable to fetch deb-archive for package plesk-php72-pspell (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-pspell=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-redis': Unable to fetch deb-archive for package plesk-php72-redis (5.3.2-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-redis=5.3.2-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-snmp': Unable to fetch deb-archive for package plesk-php72-snmp (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-snmp=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-soap': Unable to fetch deb-archive for package plesk-php72-soap (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-soap=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-sodium': Unable to fetch deb-archive for package plesk-php72-sodium (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-sodium=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-tidy': Unable to fetch deb-archive for package plesk-php72-tidy (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-tidy=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-xdebug': Unable to fetch deb-archive for package plesk-php72-xdebug (3.0.0-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-xdebug=3.0.0-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-xml': Unable to fetch deb-archive for package plesk-php72-xml (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-xml=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php72-xmlrpc': Unable to fetch deb-archive for package plesk-php72-xmlrpc (1:7.2.34-ubuntu.20.04.211108.1944): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php72-xmlrpc=1:7.2.34-ubuntu.20.04.211108.1944' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73': Unable to fetch deb-archive for package plesk-php73 (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-bcmath': Unable to fetch deb-archive for package plesk-php73-bcmath (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-bcmath=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-cli': Unable to fetch deb-archive for package plesk-php73-cli (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-cli=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-dba': Unable to fetch deb-archive for package plesk-php73-dba (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-dba=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-dev': Unable to fetch deb-archive for package plesk-php73-dev (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-dev=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-enchant': Unable to fetch deb-archive for package plesk-php73-enchant (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-enchant=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-fpm': Unable to fetch deb-archive for package plesk-php73-fpm (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-fpm=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-gd': Unable to fetch deb-archive for package plesk-php73-gd (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-gd=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-imagick': Unable to fetch deb-archive for package plesk-php73-imagick (3.6.0-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-imagick=3.6.0-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-imap': Unable to fetch deb-archive for package plesk-php73-imap (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-imap=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-intl': Unable to fetch deb-archive for package plesk-php73-intl (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-intl=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-ioncube-loader': Unable to fetch deb-archive for package plesk-php73-ioncube-loader (10.4.5-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-ioncube-loader=10.4.5-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-ldap': Unable to fetch deb-archive for package plesk-php73-ldap (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-ldap=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-mbstring': Unable to fetch deb-archive for package plesk-php73-mbstring (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-mbstring=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-mysql': Unable to fetch deb-archive for package plesk-php73-mysql (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-mysql=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-odbc': Unable to fetch deb-archive for package plesk-php73-odbc (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-odbc=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-opcache': Unable to fetch deb-archive for package plesk-php73-opcache (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-opcache=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-pdo': Unable to fetch deb-archive for package plesk-php73-pdo (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-pdo=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-pear': Unable to fetch deb-archive for package plesk-php73-pear (1.10.13-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-pear=1.10.13-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-pgsql': Unable to fetch deb-archive for package plesk-php73-pgsql (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-pgsql=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-process': Unable to fetch deb-archive for package plesk-php73-process (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-process=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-pspell': Unable to fetch deb-archive for package plesk-php73-pspell (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-pspell=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-redis': Unable to fetch deb-archive for package plesk-php73-redis (5.3.4-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y 
    plesk-php73-redis=5.3.4-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-snmp': Unable to fetch deb-archive for package plesk-php73-snmp (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-snmp=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-soap': Unable to fetch deb-archive for package plesk-php73-soap (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-soap=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-sodium': Unable to fetch deb-archive for package plesk-php73-sodium (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-sodium=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-tidy': Unable to fetch deb-archive for package plesk-php73-tidy (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-tidy=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-xdebug': Unable to fetch deb-archive for package plesk-php73-xdebug (3.1.1-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-xdebug=3.1.1-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-xml': Unable to fetch deb-archive for package plesk-php73-xml (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-xml=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'plesk-php73-xmlrpc': Unable to fetch deb-archive for package plesk-php73-xmlrpc (1:7.3.33-ubuntu.20.04.211118.1928): Command '/usr/bin/apt-get install -o Dir::Etc::sourcelist=/tmp/tmpcw0wt55v --reinstall --download-only -y plesk-php73-xmlrpc=1:7.3.33-ubuntu.20.04.211118.1928' returned non-zero exit status 100.
    WARNING: Skip fixing 'pp18.0.36-bootstrapper': Cannot find deb-archive for package pp18.0.36-bootstrapper (18.0-v.ubuntu.20.04+p18.0.36.0+t210526.1459)
    WARNING: Skip fixing 'pp18.0.37-bootstrapper': Cannot find deb-archive for package pp18.0.37-bootstrapper (18.0-v.ubuntu.20.04+p18.0.37.2+t210809.1806)
    WARNING: Skip fixing 'pp18.0.38-bootstrapper': Cannot find deb-archive for package pp18.0.38-bootstrapper (18.0-v.ubuntu.20.04+p18.0.38.2+t210913.2207)
    WARNING: Skip fixing 'pp18.0.39-bootstrapper': Cannot find deb-archive for package pp18.0.39-bootstrapper (18.0-v.ubuntu.20.04+p18.0.39.2+t211117.1817)
    WARNING: Skip fixing 'pp18.0.40-bootstrapper': Cannot find deb-archive for package pp18.0.40-bootstrapper (18.0-v.ubuntu.20.04+p18.0.40.3+t220116.0005)
    WARNING: Skip fixing 'pp18.0.41-bootstrapper': Cannot find deb-archive for package pp18.0.41-bootstrapper (18.0-v.ubuntu.20.04+p18.0.41.1+t220207.2342)
    WARNING: Skip fixing 'pp18.0.42-bootstrapper': Cannot find deb-archive for package pp18.0.42-bootstrapper (18.0-v.ubuntu.20.04+p18.0.42.1+t220314.1713)
    WARNING: Skip fixing 'pp18.0.43-bootstrapper': Cannot find deb-archive for package pp18.0.43-bootstrapper (18.0-v.ubuntu.20.04+p18.0.43.1+t220414.1850)
    WARNING: Skip fixing 'pp18.0.44-bootstrapper': Cannot find deb-archive for package pp18.0.44-bootstrapper (18.0-v.ubuntu.20.04+p18.0.44.3+t220614.1805)
    WARNING: Skip fixing 'pp18.0.45-bootstrapper': Cannot find deb-archive for package pp18.0.45-bootstrapper (18.0-v.ubuntu.20.04+p18.0.45.2+t220722.0939)
    WARNING: Skip fixing 'pp18.0.46-bootstrapper': Cannot find deb-archive for package pp18.0.46-bootstrapper (18.0-v.ubuntu.20.04+p18.0.46.2+t220920.1457)
    WARNING: Skip fixing 'pp18.0.47-bootstrapper': Cannot find deb-archive for package pp18.0.47-bootstrapper (18.0-v.ubuntu.20.04+p18.0.47.5+t221020.0801)
    WARNING: Skip fixing 'pp18.0.48-bootstrapper': Cannot find deb-archive for package pp18.0.48-bootstrapper (18.0-v.ubuntu.20.04+p18.0.48.0+t221102.1939)
    WARNING: Skip fixing 'pp18.0.49-bootstrapper': Cannot find deb-archive for package pp18.0.49-bootstrapper (18.0-v.ubuntu.20.04+p18.0.49.2+t230110.1619)
    WARNING: Skip fixing 'pp18.0.50-bootstrapper': Cannot find deb-archive for package pp18.0.50-bootstrapper (18.0-v.ubuntu.20.04+p18.0.50.2+t230213.1226)
    WARNING: Skip fixing 'pp18.0.51-bootstrapper': Cannot find deb-archive for package pp18.0.51-bootstrapper (18.0-v.ubuntu.20.04+p18.0.51.1+t230404.1037)
    WARNING: Skip fixing 'pp18.0.52-bootstrapper': Cannot find deb-archive for package pp18.0.52-bootstrapper (18.0-v.ubuntu.20.04+p18.0.52.3+t230516.1220)
    WARNING: Skip fixing 'pp18.0.53-bootstrapper': Cannot find deb-archive for package pp18.0.53-bootstrapper (18.0-v.ubuntu.20.04+p18.0.53.2+t230619.1201)
    WARNING: Skip fixing 'pp18.0.54-bootstrapper': Cannot find deb-archive for package pp18.0.54-bootstrapper (18.0-v.ubuntu.20.04+p18.0.54.4+t230824.0849)
    WARNING: Skip fixing 'pp18.0.55-bootstrapper': Cannot find deb-archive for package pp18.0.55-bootstrapper (18.0-v.ubuntu.20.04+p18.0.55.2+t230919.0741)
    WARNING: Skip fixing 'pp18.0.56-bootstrapper': Cannot find deb-archive for package pp18.0.56-bootstrapper (18.0-v.ubuntu.20.04+p18.0.56.4+t231106.1529)
    WARNING: Skip fixing 'pp18.0.57-bootstrapper': Cannot find deb-archive for package pp18.0.57-bootstrapper (18.0-v.ubuntu.20.04+p18.0.57.5+t231218.0957)
    WARNING: Skip fixing 'pp18.0.58-bootstrapper': Cannot find deb-archive for package pp18.0.58-bootstrapper (18.0-v.ubuntu.20.04+p18.0.58.2+t240122.1811)
    WARNING: Skip fixing 'pp18.0.59-bootstrapper': Cannot find deb-archive for package pp18.0.59-bootstrapper (18.0-v.ubuntu.20.04+p18.0.59.2+t240229.1010)
    WARNING: Skip fixing 'pp18.0.60-bootstrapper': Cannot find deb-archive for package pp18.0.60-bootstrapper (18.0-v.ubuntu.20.04+p18.0.60.1+t240421.1802)
    WARNING: Skip fixing 'pp18.0.61-bootstrapper': Cannot find deb-archive for package pp18.0.61-bootstrapper (18.0-v.ubuntu.20.04+p18.0.61.6+t240702.0644)
    WARNING: Skip fixing 'pp18.0.62-bootstrapper': Cannot find deb-archive for package pp18.0.62-bootstrapper (18.0-v.ubuntu.20.04+p18.0.62.2+t240724.1127)
    WARNING: Skip fixing 'pp18.0.63-bootstrapper': Cannot find deb-archive for package pp18.0.63-bootstrapper (18.0-v.ubuntu.20.04+p18.0.63.4+t240830.1128)
    WARNING: Skip fixing 'pp18.0.64-bootstrapper': Cannot find deb-archive for package pp18.0.64-bootstrapper (18.0-v.ubuntu.20.04+p18.0.64.1+t241004.1307)
    WARNING: Skip fixing 'pp18.0.65-bootstrapper': Cannot find deb-archive for package pp18.0.65-bootstrapper (18.0-v.ubuntu.20.04+p18.0.65.2+t241121.1338)
    WARNING: Skip fixing 'pp18.0.66-bootstrapper': Cannot find deb-archive for package pp18.0.66-bootstrapper (18.0-v.ubuntu.20.04+p18.0.66.2+t250106.1901)
    WARNING: Skip fixing 'pp18.0.67-bootstrapper': Cannot find deb-archive for package pp18.0.67-bootstrapper (18.0-v.ubuntu.20.04+p18.0.67.3+t250217.0844)
    WARNING: Skip fixing 'sw-engine-cli-3.36': Cannot find deb-archive for package sw-engine-cli-3.36 (3.36.0-ubuntu.20.04.210430.1632)
    WARNING: Skip fixing 'sw-engine-cli-3.37': Cannot find deb-archive for package sw-engine-cli-3.37 (3.37.2-ubuntu.20.04.210707.1232)
    WARNING: Skip fixing 'sw-engine-cli-3.38': Cannot find deb-archive for package sw-engine-cli-3.38 (3.38.0-ubuntu.20.04.210809.1937)
    WARNING: Skip fixing 'sw-engine-cli-3.39': Cannot find deb-archive for package sw-engine-cli-3.39 (3.39.1-ubuntu.20.04.210924.1832)
    WARNING: Skip fixing 'sw-engine-cli-3.40': Cannot find deb-archive for package sw-engine-cli-3.40 (3.40.1-ubuntu.20.04.211118.1959)
    WARNING: Skip fixing 'sw-engine-cli-3.41': Cannot find deb-archive for package sw-engine-cli-3.41 (3.41.1-ubuntu.20.04.220111.1225)
    WARNING: Skip fixing 'sw-engine-cli-3.42': Cannot find deb-archive for package sw-engine-cli-3.42 (3.42.1-ubuntu.20.04.220228.1507)
    WARNING: Skip fixing 'sw-engine-cli-3.43': Cannot find deb-archive for package sw-engine-cli-3.43 (3.43.2-ubuntu.20.04.220331.1322)
    WARNING: Skip fixing 'sw-engine-cli-3.44': Cannot find deb-archive for package sw-engine-cli-3.44 (3.44.0-ubuntu.20.04.220421.1713)
    WARNING: Skip fixing 'sw-engine-cli-3.45': Cannot find deb-archive for package sw-engine-cli-3.45 (3.45.0-ubuntu.20.04.220603.0903)
    WARNING: Skip fixing 'sw-engine-cli-3.46': Cannot find deb-archive for package sw-engine-cli-3.46 (3.46.0-ubuntu.20.04.220728.1331)
    WARNING: Skip fixing 'sw-engine-cli-3.47': Cannot find deb-archive for package sw-engine-cli-3.47 (3.47.2-ubuntu.20.04.220920.1221)
    WARNING: Skip fixing 'sw-engine-cli-3.48': Cannot find deb-archive for package sw-engine-cli-3.48 (3.48.0-ubuntu.20.04.221010.0840)
    WARNING: Skip fixing 'sw-engine-cli-3.49': Cannot find deb-archive for package sw-engine-cli-3.49 (3.49.0-ubuntu.20.04.221130.1057)
    WARNING: Skip fixing 'sw-engine-cli-4.50': Cannot find deb-archive for package sw-engine-cli-4.50 (4.50.0-ubuntu.20.04.230115.1423)
    WARNING: Skip fixing 'sw-engine-cli-4.51': Cannot find deb-archive for package sw-engine-cli-4.51 (4.51.0-ubuntu.20.04.230222.0826)
    WARNING: Skip fixing 'sw-engine-cli-5.53': Cannot find deb-archive for package sw-engine-cli-5.53 (5.53.2-ubuntu.20.04.230612.1943)
    WARNING: Skip fixing 'sw-engine-cli-5.54': Cannot find deb-archive for package sw-engine-cli-5.54 (5.54.1-ubuntu.20.04.230707.0531)
    WARNING: Skip fixing 'sw-engine-cli-5.55': Cannot find deb-archive for package sw-engine-cli-5.55 (5.55.1-ubuntu.20.04.230817.1224)
    WARNING: Skip fixing 'sw-engine-cli-5.56': Cannot find deb-archive for package sw-engine-cli-5.56 (5.56.1-ubuntu.20.04.230929.1446)
    WARNING: Skip fixing 'sw-engine-cli-5.57': Cannot find deb-archive for package sw-engine-cli-5.57 (5.57.1-ubuntu.20.04.231107.1000)
    WARNING: Skip fixing 'sw-engine-cli-5.58': Cannot find deb-archive for package sw-engine-cli-5.58 (5.58.2-ubuntu.20.04.231229.1122)
    WARNING: Skip fixing 'sw-engine-cli-5.59': Cannot find deb-archive for package sw-engine-cli-5.59 (5.59.2-ubuntu.20.04.240130.1409)
    WARNING: Skip fixing 'sw-engine-cli-5.60': Cannot find deb-archive for package sw-engine-cli-5.60 (5.60.1-ubuntu.20.04.240318.0906)
    WARNING: Skip fixing 'sw-engine-cli-6.61': Cannot find deb-archive for package sw-engine-cli-6.61 (6.61.1-ubuntu.20.04.240426.1113)
    WARNING: Skip fixing 'sw-engine-cli-6.62': Cannot find deb-archive for package sw-engine-cli-6.62 (6.62.1-ubuntu.20.04.240612.0902)
    WARNING: Skip fixing 'sw-engine-cli-6.63': Cannot find deb-archive for package sw-engine-cli-6.63 (6.63.0-ubuntu.20.04.240730.0658)
    WARNING: Skip fixing 'sw-engine-cli-6.64': Cannot find deb-archive for package sw-engine-cli-6.64 (6.64.1-ubuntu.20.04.240830.0854)
    WARNING: Skip fixing 'sw-engine-cli-6.65': Cannot find deb-archive for package sw-engine-cli-6.65 (6.65.1-ubuntu.20.04.241011.1503)
    WARNING: Skip fixing 'sw-engine-cli-6.66': Cannot find deb-archive for package sw-engine-cli-6.66 (6.66.2-ubuntu.20.04.241212.0946)
    WARNING: Skip fixing 'sw-engine-cli-6.67': Cannot find deb-archive for package sw-engine-cli-6.67 (6.67.2-ubuntu.20.04.2WARNING: Skip fixing 'sw-engine-cli-3.49': Cannot find deb-archive for package sw-engine-cli-3.49 (3.49.0-ubuntu.20.04.221130.1057)
    WARNING: Skip fixing 'sw-engine-cli-4.50': Cannot find deb-archive for package sw-engine-cli-4.50 (4.50.0-ubuntu.20.04.230115.1423)
    WARNING: Skip fixing 'sw-engine-cli-4.51': Cannot find deb-archive for package sw-engine-cli-4.51 (4.51.0-ubuntu.20.04.230222.0826)
    WARNING: Skip fixing 'sw-engine-cli-5.53': Cannot find deb-archive for package sw-engine-cli-5.53 (5.53.2-ubuntu.20.04.230612.1943)
    WARNING: Skip fixing 'sw-engine-cli-5.54': Cannot find deb-archive for package sw-engine-cli-5.54 (5.54.1-ubuntu.20.04.230707.0531)
    WARNING: Skip fixing 'sw-engine-cli-5.55': Cannot find deb-archive for package sw-engine-cli-5.55 (5.55.1-ubuntu.20.04.230817.1224)
    WARNING: Skip fixing 'sw-engine-cli-5.56': Cannot find deb-archive for package sw-engine-cli-5.56 (5.56.1-ubuntu.20.04.230929.1446)
    WARNING: Skip fixing 'sw-engine-cli-5.57': Cannot find deb-archive for package sw-engine-cli-5.57 (5.57.1-ubuntu.20.04.231107.1000)
    WARNING: Skip fixing 'sw-engine-cli-5.58': Cannot find deb-archive for package sw-engine-cli-5.58 (5.58.2-ubuntu.20.04.231229.1122)
    WARNING: Skip fixing 'sw-engine-cli-5.59': Cannot find deb-archive for package sw-engine-cli-5.59 (5.59.2-ubuntu.20.04.240130.1409)
    WARNING: Skip fixing 'sw-engine-cli-5.60': Cannot find deb-archive for package sw-engine-cli-5.60 (5.60.1-ubuntu.20.04.240318.0906)
    WARNING: Skip fixing 'sw-engine-cli-6.61': Cannot find deb-archive for package sw-engine-cli-6.61 (6.61.1-ubuntu.20.04.240426.1113)
    WARNING: Skip fixing 'sw-engine-cli-6.62': Cannot find deb-archive for package sw-engine-cli-6.62 (6.62.1-ubuntu.20.04.240612.0902)
    WARNING: Skip fixing 'sw-engine-cli-6.63': Cannot find deb-archive for package sw-engine-cli-6.63 (6.63.0-ubuntu.20.04.240730.0658)
    WARNING: Skip fixing 'sw-engine-cli-6.64': Cannot find deb-archive for package sw-engine-cli-6.64 (6.64.1-ubuntu.20.04.240830.0854)
    WARNING: Skip fixing 'sw-engine-cli-6.65': Cannot find deb-archive for package sw-engine-cli-6.65 (6.65.1-ubuntu.20.04.241011.1503)
    WARNING: Skip fixing 'sw-engine-cli-6.66': Cannot find deb-archive for package sw-engine-cli-6.66 (6.66.2-ubuntu.20.04.241212.0946)
    WARNING: Skip fixing 'sw-engine-cli-6.67': Cannot find deb-archive for package sw-engine-cli-6.67 (6.67.2-ubuntu.20.04.2
    50114.0939)
    WARNING: Skip fixing 'sw-librrd': Cannot find deb-archive for package sw-librrd (1.6.0.3-v.ubuntu.20.04+p18.0.41.1+t220207.1604)
    WARNING: Skip fixing 'sw-rrdtool': Cannot find deb-archive for package sw-rrdtool (1.6.0.3-v.ubuntu.20.04+p18.0.41.1+t220207.2342)

    0
  • Avatar
    Sistemas CQM
    (Edited )

    Hi:

    Recomendation to put in the help manual the update automatic of ubuntu 20.04 -→ ubuntu 22.04 is to check your apt-get is ok, and dont have a problem with grafana, because, the server fail in the dist-upgrade because a apt-get is corrupted with grafana GPG-KEY and dont do nothing and stop the proccess.

    plesk bin extension --uninstall grafana
    apt-get remove --purge grafana

    find /usr/share/grafana -type l ! -exec test -e {} \; -print

    And I move the repository, because plesk dont use the repository “grafana.list”, use plesk-ext-grafana.list:

    mv /etc/apt/sources.list.d/grafana.list /root/

    And then, the procces continued to pass to ubuntu 22.04.

    Regards!

    0
  • Avatar
    Kris Lowet

    Will Plesk also provide an upgrade script from Debian 12 to Debian 13? Thanks.

    1
  • Avatar
    Gabriel Aznarez
    (Edited )

    Hi, 

    Thanks for asking. 

    please note that the upgrade from Debian 12 to Debian 13 is not yet supported by Plesk. 

    Support for dist-upgrade and/or dist-upgrade CLI helper for this versions will be added later. For the time being the recommended way to switch to Debian 13 is using Plesk Migrator. 

    This information has been added into the Debian distributions tab under ‘Dist-upgrade from Debian 12 to Debian 13 - Information’ for future reference.

    thanks again!

    -1
  • Avatar
    Charles Masson

    Thanks Gabriel. Is there an ETA for the dist-upgrade to Debian 13 ?

    By the looks of the features portal : https://features.plesk.com/, it looks like it is not planned yet. Could you please confirm ?

    Also, looking at the portal, it looks like the team is a bit more reactive to work on Ubuntu versions than Debian. Is that correct ? If so, it might be a good idea on our end to reconsider working with Ubuntu instead of Debian.

    Thanks in advance !

    Regards.

    1

Please sign in to leave a comment.