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

Follow

Comments

34 comments

  • Avatar
    Sebastian M. Braun

    Unfortunately my vserver hosted by hosteurope does not come online again after running

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

    and rebooting after. Although there were no errors.

     

  • Avatar
    Andy

    @Sebastian: Same here ... I've read your comment too late :-(

  • Avatar
    Nikolay Voytko

    @Sebastian, @Andy it will be great if you can shed some light on the issues that you faced.

  • Avatar
    Andy

    Only the pre-installed version and their updates are usable.
    A dist-upgrade attempt will result in a system that is no longer running after a reboot.

    I'm still waiting for the backup process of 300 gigabytes (for 6 hours) to repair this bullshit ... please put a hint right over the call.


    Reason: 
    The virtualization software of hosteurope is probably not compatible with the updated kernel and no longer find the VM.
    @See: https://www.hosteurope.de/faq/server/server-allgemeines/selbst-installation-sicherheitsupdates/

  • Avatar
    Dimitar Mustakov

    Hi,

    @Sebastian and @Andy are problems solved?

    I need to upgrade my debian server with plesk12.5 from wheezy to jessie this weekend. Can you share any recommendations about this upgrade?

     

  • Avatar
    Alexander Tsmokalyuk

    @Andy please tell me what virtualization type is used. You can use "virt-what" utility to check it.

  • Avatar
    Sebastian M. Braun (Edited )

    My "Solution": I ordered a new clean ubuntu 16.04 and installed plesk by myself. Very disappointing.

  • Avatar
    Marco Marsala

    Prevent do-release-upgrade to be run directly or at least inject on it a clear warning message requesting confirmation.

    Plesk adds its pretty text to the SSH greeting message, so it should be doable. As per this KB article, you have to run a Plesk script; forgetting that and running do-release-upgrade directly may cause high troubles.

     

  • Avatar
    Marco Marsala

    Updating from Ubuntu 14.04 to Ubuntu 16.04.1 using do-release-upgrade will fail because MySQL is updated from 5.5 to 5.7, that is unsupported update path as per MySQL official documentation. Your script should do these pre-checks and prevent upgrade or automatically solve the issue before the upgrade.

  • Avatar
    Bulat Tsydenov

    @Marco, did you check Dist-upgrade potential issues article? Maybe it contains the issue you are talking about and the solution for that.

  • Avatar
    Marco Marsala

    @Bulat Tsydenov Yes I do and this is not listed. It seems like a bug, infact running the script as described in this article on a clean Ubuntu 14.04 installation, will upgrade MySQL 5.5 to 5.7 that is an unsupported upgrade. Too, command 'update-alternatives' is not run. This will work only if MySQL was manually upgraded to 5.6 before, but this is not mentioned anywhere.

  • Avatar
    Marco Marsala (Edited )

    Beware after upgrading from Ubuntu 14 to 16, cron jos set to be run with "PHP from OS vendor" won't run anymore, failing with error "/bin/sh: /usr/bin/php5: No such file or directory" because PHP 5 is not available anymore.

    "plesk repair" tool won't regenerate cron jobs.

    You have to fix them manually, just open them one by one from Plesk UI, and hit OK button. This will be enough to regenerate cron files.

    The issue maybe related to the fact that the "Use PHP version" dropdown still shows PHP 5.5.9 from OS vendor after upgrade. This maybe happens because there are residual 5.5.9 packages in the system that wasn't purged during upgrade.

  • Avatar
    Denis Bykov

    @Marco, I have reproduced the behavior on a test server and created a request to developers to find out if this is a bug.

    All updates regarding the investigation will be sent to your email.

    Thank you for the feedback.

  • Avatar
    Marco Marsala (Edited )

    Please note that after upgrade, MySQL event scheduler won't be enabled again, if it was before the upgrade, and you should fix that manually.

  • Avatar
    Robert Asilbekov

    @Marco we have created an internal request. You'll be notified via email.

    Thank you for the feedback.

     
  • Avatar
    Alexander Tsmokalyuk

    @Marco a solution was found and sent to your email. "General information" section of this article was updated. Thank you.

  • Avatar
    Marian Feiler

    Will there be pre and post upgrade helper files for deb8 to deb 9?

  • Avatar
    Ivan Postnikov

    @Marian

    Instruction for an upgrade to Debian 9 will be added to this article soon.

    Click "Follow" to be notified when the article will be updated.

  • Avatar
    Marco Marsala

    If MySQL event scheduler (SET GLOBAL event_scheduler = ON) was enabled before the upgrade, it won't be enabled again after following this KB article, without any notice to user.

  • Avatar
    Trung Ma

    @Ivan I'm upgrading OS from Debian 7 to 8. After run file /opt/psa/bin/distupgrade.helper.deb7-deb8_pre.x64.sh , I got the error message as picure below

    What should i do?

    Regards,

  • Avatar
    Ivan Postnikov

    @Trung, such errors are usually caused by incompatibility of Plesk with repositories that are configured on the server.

    Please, make sure that standard repositories only are configured on the server and restart the script.

  • Avatar
    Florent

    Hi, since Ubuntu 18.04.1 was released a month ago, when the upgrade will be available ?

    + Do you recommend an upgrade or a migration on a fresh install ?

    Thanks

  • Avatar
    Ivan Postnikov

    Hello @Florent, the upgrade will be available soon. There is no exact ETA but this article will be updated with the corresponding information.

    > Do you recommend an upgrade or a migration on a fresh install?

    Both methods are ok and the choice is up to you. 

  • Avatar
    Janusz Kucharczyk (Edited )

    Hi, i try to update my Debian 8 up tp 9 with Plesk 17.8.11

    but it dies everytime at the 'Bootstrapper repair actions failed'

    Take a look:

    Actually I couldn't figure out how to fix this, do you have any idea?

    (And this is the Screenshot out of the told .log file...)

    Please help me. :D

    Thanks in advance and kind regards.

  • Avatar
    Bato Tsydenov

    @Janusz Kucharczyk

    Please check the following article:

    https://support.plesk.com/hc/en-us/articles/213373289-Dist-upgrade-potential-issues

    If the article is not helpful I would recommend you submitting a Support ticket.

  • Avatar
    Μίστερ Μολ

    I attempted today the upgrade from debian 8 to 9 following the above instructions. All went fine (except in the beginning that I had to manually remove some atomicorp repos [1] which were stopping the procedure), until at the end of the dist-upgrade that I got:

    Fetched 76.2 MB in 21s (3472 kB/s)
    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

    Just out of curiosity I tried to run the post upgrade script (# /opt/psa/bin/distupgrade.helper.deb8-deb9_post.x64.sh) but there was no such script.

    I rebooted the server, everything looked fine, I entered Plesk and at the home screen I saw:
    Debian 9.8
    Product Plesk Onyx
    Version 17.8.11 Update #45

    It looked as if the upgrade had succeeded. But this being a critical server, I could not risk it, so I restored the server from the snapshot I had taken just before.

    So, what happened? Why those errors? Should I try again changing something?

    [1]
    Err http://updates.atomicorp.com stretch/main amd64 Packages
    404 Not Found [IP: 158.69.253.161 80]
    Err http://updates.atomicorp.com stretch/main i386 Packages
    404 Not Found [IP: 158.69.253.161 80]
    Ign http://updates.atomicorp.com stretch/main Translation-en
    Fetched 111 kB in 6s (17.8 kB/s)
    W: Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/stretch/main/binary-amd64/Packages 404 Not Found [IP: 158.69.253.161 80]
    W: Failed to fetch http://updates.atomicorp.com/channels/tortix-common/debian/dists/stretch/main/binary-i386/Packages 404 Not Found [IP: 158.69.253.161 80]

     

  • Avatar
    Alexandr Nikolaenko

    Hello Μίστερ Μολ,

    The case looks quite complex to discuss it in article comments. Please submit a ticket for us and we will be glad to investigate the issue and assist you.

  • Avatar
    Μίστερ Μολ

    Hi @Alexandr.

    Thanks for your offer, but I cannot submit a ticket since I'm on a licence key bought from Hetzner, which does not provide free support. And my company is not willing to pay for support on a thing that looks like a plesk bug... It's a deadlock! Can you help otherwise?

  • Avatar
    Ivan Postnikov

    Μίστερ Μολ,

    Thank you for the feedback, I have provided an answer in this article: https://support.plesk.com/hc/en-us/articles/213953025

Please sign in to leave a comment.

Have more questions? Submit a request