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

Follow

Comments

65 comments

  • Avatar
    Jan Bludau

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

    0
    Comment actions Permalink
  • Avatar
    Nikita Nikushkin

    Hi @Jan Bludau,

    Could please provide us with the OS?

    Thank you!

    0
    Comment actions Permalink
  • Avatar
    Oliver Mueller

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

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oliver,

    Thank you for the feedback.

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

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

    0
    Comment actions Permalink
  • Avatar
    Oliver Mueller

    Still no ETA? Even an approximation would help.

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oliver,

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

    -1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Oliver,

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

    The ETA will be available later. 

    News will be added to this article.

    -1
    Comment actions Permalink
  • Avatar
    Elisabeth Kahnert

    Upgrade from Ubuntu 16 to Ubuntu 18 is needed

    1
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    @Elisabeth,

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

    -2
    Comment actions Permalink
  • Avatar
    Elisabeth Kahnert

    @Julian Bonpland Mignaquy

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

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

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

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

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

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

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

    Can anyone help me? Thank you

     

     

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Sandonanet s.n.c.,

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

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

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

    0
    Comment actions Permalink
  • Avatar
    Dirk Riehle

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

    1
    Comment actions Permalink
  • Avatar
    Oliver Mueller

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

     

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

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

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

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

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

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

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

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

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

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

     

    2
    Comment actions Permalink
  • Avatar
    Michael

    +1

    I am also waiting for this upgrade support!

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

    2
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Oliver Mueller and Michael

    Thank you for the feedback.

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

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

     

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

    There're no such plans.

     

    > more infos on this topic is expected

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

    Thank you for understanding.

    -2
    Comment actions Permalink
  • Avatar
    Jan Bludau

    +1

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

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

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

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

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

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Vương Công Minh

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

    Consider upgrading the test server before production one.

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

    -1
    Comment actions Permalink
  • Avatar
    putinluver127

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

    Plesk

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

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

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

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

    START Distupgrade
    START Distupgrade

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

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

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

    So this is didn't quite work as intended:

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

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

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

    Turns out what happened is:

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

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

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Mark-Oliver Wolter

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

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

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

    -1
    Comment actions Permalink
  • Avatar
    b_p

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

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

    Best regards,

    1
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello,

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

    2
    Comment actions Permalink
  • Avatar
    b_p

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

    1
    Comment actions Permalink
  • Avatar
    Adrian Czternasty (Edited )

    Hi 

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

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

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

    Maybe it will some helps.

    Regards

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request