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

Follow

Comments

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

    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

Please sign in to leave a comment.

Have more questions? Submit a request