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

Follow

Comments

92 comments

  • Avatar
    Elisabeth Kahnert

    We are still waiting for this upgrade guide from Ubuntu 16 to 18.

    0
    Comment actions Permalink
  • Avatar
    FrHE

    I hope you can assist me with the following:

    I am looking for the best way to proceed an update of Debian 7.11 with Plesk Onyx 17.5.3 to newer Debian and Plesk Obsidian.

    I have already made sure that PHP 5.4 is not needed anymore and there are no more domains running on it.

    As I have seen for Obsidian a minimum Debian 9 is needed and I think this version is fine as it is supported until 2022.

    Plesk Onyx seems to run on Debian 8 and Debian 9.

    I am specially interested in what is the best way going up to the best new version?

    Would this be fine?

    First dist upgrade to Debian 8 than to Debian 9 than Onyx to Obsidian?

    Is there a distupgrade possibility within Plesk also?

    I will have assistance of course, but it would be helpful getting more information about the order of the single steps (btw. corrections) to perform.

    Many thanks

     

    0
    Comment actions Permalink
  • Avatar
    Kevin Dorlas

    This is taking too long.. There has to be a upgrade from 16 to 18 and 18 to 20 aswel, cuz 18 is already outdated nowadays..

    1
    Comment actions Permalink
  • Avatar
    Dirk

    Helloooooo? What about the overdue and long-promised upgrade from Ubuntu 16 to 18?

    1
    Comment actions Permalink
  • Avatar
    Elisabeth Kahnert

    Promised for the end of october. And we are still waiting for this upgrade guide from Ubuntu 16 to 18 in december.

    0
    Comment actions Permalink
  • Avatar
    Francisco Garcia

    Hi,

    For all those waiting for the guide for newer operating systems, please be patient since we're finishing our tests and verifications that the procedure is safe to apply and won't break your servers :)

    Ubuntu 16->18 distro-upgrade is going to be public very soon (during this week I believe).

    For the procedure of Ubuntu 18->20 and Debian 9->10, to be honest, we're having some troubles with package management and dependencies while the distro-upgrade that without dirty hacks are difficult to overcome, something not suitable for inexperienced users.

    Thanks for your patience.

    1
    Comment actions Permalink
  • Avatar
    Francisco Garcia

    As said yesterday, the guide is published now with Ubuntu 16->18 Distro upgrade procedure.

    The other 2 (Ubuntu 18->20 and Debian 9->10) are on their way.

    Thanks for your patience.

    0
    Comment actions Permalink
  • Avatar
    Dirk

    Has anyone tested 16 -> 18 yet?

    0
    Comment actions Permalink
  • Avatar
    Patrick Lahni

    Dirk Didn't go well for me at all.  For starters, https://packages.grafana.com/oss/ubuntu doesn't even exist for sources.list.  Per grafana, it should be https://packages.grafana.com/oss/deb so I'm not convinced this process was very well vetted.  Step #7 isn't super clear.  In my instance, I have 5 separate URLs in my plesk.list.  I assume they mean the PSA_* URL.  I used their example and it immediately failed because of libcurl3.  Installing libcurl4 proceeded to update a ton of packages.  Ultimately it had issues with mariadb and it seems it wanted to update the database.

    I honestly just got fed up with how abysmal this upgrade process is, how long it took to get these instructions, I've got very little faith in the product or their ability to provide a safe upgrade path.  I wasn't about to attempt this again from 18.04 to 20.04 because that sounds like even more of a train wreck.  I took a complete server backup prior to attempting to upgrade.  I've been meaning to reorganize a few things so I'm taking the opportunity to just install 20.04 fresh and reinstall Plesk on top of that.  Hopefully my backup imports smoothly but again, I've very little faith at this point.

    I implore the Plesk team to really make this process a priority in the future.

    0
    Comment actions Permalink
  • Avatar
    Marc López

    Yes, Patrick, you are absolutely right, the repositories for Grafana are wrong and should be as you correctly pointed out. Thanks for bringing this to my attention! I've proceeded to perform the change in the guide and set it properly, it should be right now.

    As for the rest of the problems/concerns, unfortunately, there is no easy way to perform such a process upgrading the distribution thus, this is as well the main reason why it is not recommended and, what we recommend instead, is to perform a migration. The result should be cleaner and more pleasant.

    -1
    Comment actions Permalink
  • Avatar
    Oliver Mueller

    The recommended upgrade path using the migration guide is an economical disaster, to say the least.

    Only because plesk fell short on all promises, we had to go with the migration guide a couple of months ago. We had so much pressure from our clients, that we had to upgrade, especially because many packages had been at their end of life. One of the reason is that not all ubuntu packages have long time support. Anyway. The migration took us weeks to prepare and complete. The migration assistant is so poorly build and has so many bugs, that many things are not getting migrated even though they are part of plesk itself. Worse than that is of course all the other stuff. If you are using a server for many years for many clients, you will customise it to your and your clients' needs. Plesk is just offering basic packages (web, apps, dns, mail) and it is obvious that admins have to tweak the server around plesk.

    The migration took hours, which was downtime, and even with weeks of preparation we still had to fix so many things afterwards. The customers were annoyed and we too.

    And I just want to repeat myself: the migration was an economical catastrophe for us. Just make the calculation for yourself. How many client you have to have to get paid for this immense effort and loss of confidence? A migration is the worst upgrade path and should not be the recommended one!

    So far plesk has not delivered anything they promised, not even a good nor expectable excuse.

    1
    Comment actions Permalink
  • Avatar
    Santiago

    Hello, it's already safe to upgrade a Plesk Ubuntu 18.04 installation to Ubuntu 20.x LTS version?

    Thank you in advance.-

    0
    Comment actions Permalink
  • Avatar
    kongo09

    Thanks for all the comments. This makes me stop to attempt the upgrade. I started following the 16 -> 18 guide above but step 7 is so super unclear that I wonder how this could end up in a guide in the first place.

    0
    Comment actions Permalink
  • Avatar
    Dirk

    I also haven't tried yet, because of step #7. Could anyone make this a little more precise?

    0
    Comment actions Permalink
  • Avatar
    Markus (Edited )

    Marc López

    Thanks a lot for the hard work of the whole Plesk team realizing do-release-upgrade from Ubuntu 18 to 20. Some people always want the newest features, but they don't realize that by uncountable cross-dependencies it is more and more impossible to upgrade the OS under these tons of services and dependencies.

    Question: Is it an typo/text error or is it real that only the PHP 8 is a bionic package and all other packages are focal? Please look in the tutorial Ubuntu 18 to 20. sources list:

    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/ bionic all
    deb https://packages.grafana.com/oss/deb stable main

    For me it looks like a typo. It should be also "focal", isn't it.

    Lots of greets (I think I will try it)

    0
    Comment actions Permalink
  • Avatar
    Marc López

    Hello Markus,

    You are absolutely right, it was a typo. I've modified the article accordingly.

    Thank you very much for bringing this to my attention! :)

     

    0
    Comment actions Permalink
  • Avatar
    Markus (Edited )

    Thanks, too. I want to do the upgrade now. therefor I've another two questions. I use a dedicated server by Ionos in Germany. I know you or Plesk work together in some ways. Upgrade to Ubuntu 20 is shown in shell/cli since a few months.Sorry for the questions, but I want to take as little as possible risks.

    Is it possible to use the 1and1 repositiories/sources or do you suggest better and absolutely the sources by Aachen university from the tutorial?

    On my server MariaDB is running. Since my last MariaDB upgrade from 10.4 to 10.5(.8) the configuration paths seemed to be changed a little. my.cnf is a link to /etc/mysql/mariadb.cnf (to set global defaults). I would set here the innodb_fast_shutdown=0 in the [mysqld] section. Is it right, or perhaps /etc/mysql/mariadb.conf.d/50-server.cnf where I already made Fine tuning settings?

     

    0
    Comment actions Permalink
  • Avatar
    Marc López

    Dirk kongo09 Oliver Mueller Patrick Lahni

    I am glad to announce that the guide for Ubuntu 16 to Ubuntu 18 has been reworked and simplified.

    Thank you very much for your feedback guys, really appreciate it :)

    0
    Comment actions Permalink
  • Avatar
    Marc López (Edited )

    Markus

    Is it possible to use the 1and1 repositiories/sources or do you suggest better and absolutely the sources by Aachen university from the tutorial?

    Repositories had been changed for the Ubuntu generic ones so it does not lead to any misunderstanding. You may be able to use the ones from 1and1 but I suggest you to use Ubuntu ones :)

    On my server MariaDB is running. Since my last MariaDB upgrade from 10.4 to 10.5(.8) the configuration paths seemed to be changed a little. my.cnf is a link to /etc/mysql/mariadb.cnf (to set global defaults). I would set here the innodb_fast_shutdown=0 in the [mysqld] section. Is it right, or perhaps /etc/mysql/mariadb.conf.d/50-server.cnf where I already made Fine tuning settings?

    The file you can modify for that is, as you point out, /etc/mysql/mariadb.conf.d/50-server.cnf, this has been clarified as well in the guide to be more precise for both distributions, 16 and 18.

    Thanks for bringing this to my attention!

    0
    Comment actions Permalink
  • Avatar
    kongo09

    Marc López thanks for updating and reworking the guide!

    I am glad to announce that the guide for Ubuntu 16 to Ubuntu 18 has been reworked and simplified.

    One thing remained unclear for me. You mention in the beginning:

    Remote management module must be installed on the server

    What is that and where do I find that? I cannot see any extension with that name and Google search only turns up articles about WordPress. Could you please shine some light on this?

    0
    Comment actions Permalink
  • Avatar
    Andy B

    Very skeptically, I gave this a shot, upgrade from:
    Ubuntu 16 > Ubuntu 18

    and it failed. 

    The first issue I had at step 6, which failed.
    After several `apt-get upgrade` and `apt-get dist-upgrade` and retry 6 it worked. 

    Then... all good :) just `plesk` was missing(command not found), web configs were not working. 

    I had to restore the snapshot. 

    0
    Comment actions Permalink
  • Avatar
    Francisco Garcia

    Hi Andy B,

    Did you check if within one of those apt-get dist-upgrade the APT was suggesting to remove some packages?
    This plesk command not found means highly probable that plesk packages were removed due to some dependency.

    0
    Comment actions Permalink
  • Avatar
    Andy B

    Francisco Garcia I am not sure. I had to rollback the snapshot, gave it up as it seems very risky. 
    I am setting up a new VPS and transfer everything to the new server. 

    When this is done, I can play again with the old one. 

    0
    Comment actions Permalink
  • Avatar
    Lars Oeschey (Edited )

    I'm trying the dist-upgrade from ubuntu 16 to 18. I followed the steps, but at the latest one, the actual dist-upgrade nothing happens... Perhaps my sources list is wrong?

    deb ftp://ftp.stratoserver.net/pub/linux/ubuntu xenial main restricted universe
    deb-src ftp://ftp.stratoserver.net/pub/linux/ubuntu xenial main restricted universe

    deb ftp://ftp.stratoserver.net/pub/linux/ubuntu xenial-updates main restricted universe
    deb-src ftp://ftp.stratoserver.net/pub/linux/ubuntu xenial-updates main restricted universe

    deb ftp://ftp.stratoserver.net/pub/linux/ubuntu xenial-security main restricted universe
    deb-src ftp://ftp.stratoserver.net/pub/linux/ubuntu xenial-security main restricted universe

    deb http://updates.atomicorp.com/channels/tortix-common/debian xenial main

    deb http://autoinstall.plesk.com/PSA_18.0.33/ bionic all

    root@h1884536:~# apt-get dist-upgrade
    Paketlisten werden gelesen... Fertig
    Abhängigkeitsbaum wird aufgebaut.
    Statusinformationen werden eingelesen.... Fertig
    Paketaktualisierung (Upgrade) wird berechnet... Fertig
    0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

    0
    Comment actions Permalink
  • Avatar
    Francisco Garcia

    Hi Lars Oeschey,

    Performing the dist-upgrade > Step 1 isn't performed properly, as in your case you're still using Xenial (Ubuntu 16), while it should be all Bionic (Ubuntu 18).

    https://wiki.ubuntu.com/Releases

    Please, before executing the guide blindly, read it properly and understand each step what it does, and its purpose.

    Distro-upgrade is quite critical and may result in a complete disaster if something isn't followed properly and there's no server snapshot to rollback.

    0
    Comment actions Permalink
  • Avatar
    Lars Oeschey (Edited )

    I think you mean this?

    deb http://autoinstall.plesk.com/PSA_18.0.33/ bionic all

    was addedd to the sources list (since I'm on 18.0.33)

    0
    Comment actions Permalink
  • Avatar
    Jonathan B. (Edited )

    Hello!

    I have successfully upgrade our debian 9 to debian 10 with plesk version 18.0.34. But here my experience :

    When you can leave with a bit down time, then don't install msmtp, because it will delete all your postfix and dovecot settings. That is bad when you have, like us, custom settings. Just stop this services, before the update process.

    I would also disable all the pages, so there is no access to it and stop mariaDB server. In case there is a problem and you have roll back to an snapshot, you don't lose any data, which was written to it.

    Don't delete all the repos in /etc/apt/sources.list.d/. Edit them according to the new urls from description. Add then only the debian repos in /etc/apt/sources.list. This will prevent any warings later about double entry when you run "plesk installer update", like what you see here: https://talk.plesk.com/threads/duplicates-in-apt.355955/#post-879111

    After dist-upgrade my bind9 server was not working anymore, so I have to follow this two steps: permission and mkdir-run-Permission-denied

    When running "plesk installer", I reinstall postfix and Spamassassin. But later my dovecot was not working two, this I fixed with: "openssl dhparam -out /opt/psa/etc/dhparams1024.pem 4096"

    Then I had also a problem with spamassassin, which I fix with: Connection-refused. Some how the service was als disabled, so I had to enable them.

    I also needed to enable pc-remote service.

    0
    Comment actions Permalink
  • Avatar
    Jan Gudmundsson

    this did not go well for me...

    0
    Comment actions Permalink
  • Avatar
    Markku Valkonen (Edited )

    I was quite scared to do this after so many comments with problems, but update ubuntu 18 -> 20 went smoothly. No problems whatsoever.

    And migration was not really option for me, since almost all my domains have DNSSEC signatures and they cannot be migrated.

    0
    Comment actions Permalink
  • Avatar
    Lars Oeschey

    a question regarding the 18->20 upgrade, I have only mysql DBs, do I need to convert to MariaDB?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request