Resolved Upgrade Ubuntu 16.04 LTS to 18.04

[Hoerli]

Hey!
I try to make the upgrade from Ubuntu 16 to 18 but it wont work

I read in a view posts on some websites, that its possible to upgrade to 18 if i use Plesk Onxy 17.8.
I have Onxy 17.8.11 installed.

If i run "do-release-upgrade", it cancel the upgrade.
This is the console-log:

Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,253 kB]
Fetched 1,254 kB in 0s (0 B/s)
authenticate 'artful.tar.gz' against 'artful.tar.gz.gpg'
extracting 'artful.tar.gz'
404 Not Found, E:Failed to fetch
http://autoinstall.plesk.com/ubuntu/PHP70_17/dists/artful/all/binary-amd64/Packages
404 Not Found, E:Failed to fetch
http://updates.atomicorp.com/channels/tortix-common/debian/dists/artful/main/binary-amd64/Packages
404 Not Found [IP: 173.203.184.213 80], E:Failed to fetch
http://autoinstall.plesk.com/ubuntu/PHP71_17/dists/artful/all/binary-amd64/Packages
404 Not Found, E:Failed to fetch
http://autoinstall.plesk.com/ubuntu/PHP72_17/dists/artful/all/binary-amd64/Packages
404 Not Found, E:Some index files failed to download. They have been
ignored, or old ones used instead.


Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command detached from window (Mon Jun 25 07:48:14 2018) ===
=== Command terminated with exit status 1 (Mon Jun 25 07:48:24 2018) ===

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Get:1 http://37.157.253.141/ubuntu xenial InRelease [247 kB]
Get:2 http://37.157.253.141/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://37.157.253.141/ubuntu-security xenial-security InRelease [107 kB]
Hit http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 xenial InRelease
Hit http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12 all InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP52_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP53_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP54_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP55_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP56_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP70_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP71_17 xenial InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP72_17 xenial InRelease
Hit http://updates.atomicorp.com/channels/tortix-common/debian xenial InRelease
Hit http://repo.cloudlinux.com/kernelcare-debian/6 stable InRelease
Hit https://apt.dockerproject.org/repo ubuntu-xenial InRelease
Fetched 463 kB in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
No candidate ver:  dgri-report
No candidate ver:  plesk-py27

Updating repository information

No valid mirror found

While scanning your repository information no mirror entry for the
upgrade was found. This can happen if you run an internal mirror or
if the mirror information is out of date.

Do you want to rewrite your 'sources.list' file anyway? If you choose
'Yes' here it will update all 'xenial' to 'artful' entries.
If you select 'No' the upgrade will cancel.

Continue [yN]
Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command detached from window (Mon Jun 25 07:58:18 2018) ===
=== Command terminated with exit status 1 (Mon Jun 25 07:58:28 2018) ===

Some packages were not found, for whatever reason...
What can I do to make it work?

I have never edited any source lists nor imported updates from other sources. All config data should still be standard.

 

[IgorG]

Change Log for Plesk

• Ubuntu does not support dist-upgrade from Ubuntu 16.04 to Ubuntu 18.04 yet and neither does Plesk. Ubuntu is expected to release Ubuntu 18.04.1, which supports dist-upgrade, in late July. Soon after the release, we will add dist-upgrade support from Ubuntu 16.04 to Ubuntu 18.04 to Plesk.

 

[trialotto]

@Hoerli

In addition to the answer of @IgorG, it has to be stated that it is highly recommended to NOT do an in-place (release) upgrade of Ubuntu on a server that contains active Plesk instances: for many (obvious) reasons, it often is better to use a clean install of Plesk on a clean Ubuntu 18.04 LTS server, to which all domains/subscriptions on the old server will be migrated via the Plesk Migrator Extension.

In short, migrating all existing domains/subscriptions to a clean Plesk instance and server will save you a lot of headaches and problems (some of them cannot be solved!).

Kind regards......

 

[Hoerli]

Thanks for the answers.
I read in a view Websites, that the function for directly upgrade should be ready last week ... whatever.

@trialotto Do you have some documentation for that, maby in german? That will be the first time for me
I did a upgrade from Ubuntu 14 to 16 and plesk work fine.
But I would actually prefer a clean installation.
My hoster does not currently offer Ubuntu 18 as a clean new installation, so I would probably have to upgrade myself.

 

[trialotto]

@Hoerli

This statement

I did a upgrade from Ubuntu 14 to 16 and plesk work fine.

is normally correct, but in some upgrade scenario's the upgrade process will break the entire server (for instance, when MySQL server is at version 5.6 before upgrade and a proper restart of the MySQL server fails).

Furthermore, without the do-release-upgrade command, the Ubuntu version will not upgrade properly: some (read: a lot) dependencies are not met in the upgrade process.

With respect to the statement

My hoster does not currently offer Ubuntu 18 as a clean new installation, so I would probably have to upgrade myself.

I have to mention that it is probably not recommended to do the upgrade yourself: in the short run, you will get some issues (read: if your hosting provider does not support the Ubuntu 18.04 LTS version, so will the repositories of your hosting provider not contain the proper packages, which can be troublesome in many ways) and in the long run, one can get some peculiar issues (for instance, severe problems related to Linux kernels. In the case of VPSes, the lack of support for specific versions is mostly related to lack of support on the host server on which the VPS resides: a release upgrade of Ubuntu on the VPS is possible, but there is either an old kernel present for which Ubuntu support will stop in a couple of years or there is a kernel that conflicts with the host system).

In essence, I would highly recommend to host your servers at hosting provider that has more up-to-date systems.

Finally, with respect to the statement

Do you have some documentation for that, maby in german? That will be the first time for me

I can simply answer that I do not have German documentation, but the whole process is staightforward: launch a new server with Ubuntu 16.04 LTS or 18.04 LTS, install Plesk, install the Plesk Migrator and migrate all domains to the new server (and afterwards, point DNS to the new server...... and you are finished).

There is nothing special to the whole process, except that it is a bit time-consuming (time for some drinks and relaxation!)

Regards............