• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue Upgrade ubuntu from 14.04 to 16.04

stzi

New Pleskian
Hello,

I tried to upgrade my server from ubuntu 14.04 to 16.04.

I tried the update on two ways:
[1] Dist-Upgrade Support
/opt/psa/bin/distupgrade.helper.ubt14-ubt16.x64.sh
reboot
/opt/psa/bin/distupgrade.helper.ubt14-ubt16.x64.sh​
[2] Unterstützung des Dist-Upgrades
/usr/local/psa/bin/distupgrade.helper.ubt14-ubt16_pre.x64.sh
do-release-upgrade
reboot
/usr/local/psa/bin/distupgrade.helper.ubt14-ubt16_post.x64.sh (not available)​

With the way [1]: It was not possible to log in after the reboot (on any way).

With the way [2]: It was only possible to log in with a web console (I think it is a "direct" console, no ssh.), but it was not possible to work/fix anything with the console. I saw, that there is not network available (eth0).

I tried also a combination of [1] and [2]:
/usr/local/psa/bin/distupgrade.helper.ubt14-ubt16_pre.x64.sh
/usr/local/psa/bin/distupgrade.helper.ubt14-ubt16.x64.sh​
reboot
/usr/local/psa/bin/distupgrade.helper.ubt14-ubt16.x64.sh
It was also not possible to log in after the reboot.

I have also done a diff between the files in /opt/psa/bin/ and /usr/local/psa/bin/. The diff say there are no differences.

My current versions are:
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

# plesk version
Product version: Plesk Onyx 17.5.3 Update #37
Update date: 2018/01/17 06:26
Build date: 2017/03/17 16:00
OS version: Ubuntu 14.04
Revision: 55d1b49a272f44666e1920eca8b6e4da449a38cd
Architecture: 64-bit
Wrapper version: 1.2

Do you have any idea? Should I provide more informations, what information?

Stefan
 
I would not mix different methods and use only one official method described in documentation Dist-Upgrade Support
You wrote
With the way [1]: It was not possible to log in after the reboot (on any way).
It is better to fix this post-upgrade problem than run other methods, etc.
Habe you tried to fix it at least with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation

?
 
Sure, it should be fixed.

I have also tried your comments:
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation
?
But, I get same result.

The ifconfig says again only, that docker0 and lo available, no eth0.

I got also the message from the boot screen:
[FAILED] Failed to start Load Kernel Modules.
[FAILED] Failed to start Raise network interfaces.

I got also the option to look into the systemctl:
# systemctl status systemd-modules-load.service
- systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-loa.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) <timestamp>
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 182 ExexStart=/lib/systemd-modules-load (code-exited, status=1/FAILURE)
Main PID: 182 (code-exited, status=1/FAILURE)

# systemctl status networking.service
- networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor present: enabled)
Drop-In: /run/systemd/generator/networking.service.d
'-50-insserv.conf-$network.conf
Active: failed (Result: exit-code) <timestamp>
Docs: man:interfaces(5)
Process: 544 ExecStart=/sbin/ifup -a --read-enviroment (code=exit, status=1/FAILURE)
Process: 544 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-enviroment --list --exclud<ent of the screen>
Main PID: 544 (code=exit, status=1/FAILURE)
<usual log messages of ifup[544] and systemd[1] with the same information>
e.g.: ifup[544] Failed to bring up eth0.

Stefan
 
Back
Top