• 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

Resolved Failted Attempted To Upgrade - Now Styling Gone

TIMinion

New Pleskian
I have a IONOS Linux Cloud CentOS 7 Server with comes with a Plesk Onyx (Unlimited Domains) licence.

I have just attempted to upgrade my Plesk version from Plesk Onyx 17.8.11 to the latest version, listed to be Obsidian, however an error came back upon attempting to do this, please see attached "plesk installation log.txt" within attached "plesk installation log.zip".

Bash:
Fatal error during packages installation:

[u'ERROR with transaction check vs depsolve:', 'plesk-service-node-utilities >= 18.0 is needed by psa-mail-driver-common-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64', 'plesk-web-hosting >= 18.0 is needed by plesk-roundcube-1.4.8-2.centos.7+p18.0.30.2+t200930.1355.noarch', 'plesk-service-node-utilities >= 18.0 is needed by plesk-core-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64', 'psa-libpam-plesk is needed by plesk-core-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64', 'plesk-web-hosting >= 18.0 is needed by psa-horde-5.2.23-2.centos.7+p18.0.30.2+t200930.1355.noarch'] YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'plesk-service-node-utilities >= 18.0 is needed by psa-mail-driver-common-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64', 'plesk-web-hosting >= 18.0 is needed by plesk-roundcube-1.4.8-2.centos.7+p18.0.30.2+t200930.1355.noarch', 'plesk-service-node-utilities >= 18.0 is needed by plesk-core-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64', 'psa-libpam-plesk is needed by plesk-core-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64', 'plesk-web-hosting

>= 18.0 is needed by psa-horde-5.2.23-2.centos.7+p18.0.30.2+t200930.1355.noarch']

Since attempting to upgrade, my plesk is now showing without any stylesheet
1602879157275.png

I was told that this output may help with finding a solution to the problem I'm facing, however I know very little of what any of this means.
Bash:
[root@localhost ~]# rpm -qa |grep psa
psa-libpam-plesk-17.8.11-cos7.build1708180301.19.x86_64
psa-mod_sysenv-0.2-2.centos.7+p18.0.30.0+t200825.1337.x86_64
psa-proftpd-1.3.6c-cos7.build1708200416.15.x86_64
psa-libpam-plesk-18.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64
psa-passwd-5.0.7-cos7.build1708180425.15.noarch
psa-vhost-18.0-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-updates-18.0-2.centos.7+p18.0.27.0+t200421.1927.noarch
psa-pylibplesk-17.8.11-cos7.build1708180301.19.x86_64
psa-turba-4.2.25-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-mnemo-4.2.14-cos7.build1708180425.15.noarch
psa-imp-6.2.24.1-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-horde-5.2.23-cos7.build1708200923.13.noarch
psa-mod_fcgid-2.3.9.5-centos7.18020211.x86_64
psa-pear-1.10.5-20180124.centos7.18012417.noarch
psa-imp-6.2.21.1-cos7.build1708180425.15.noarch
psa-kronolith-4.2.23-cos7.build1708180425.15.noarch
psa-mod_proxy-2.4.6-centos7.17122714.x86_64
psa-locale-base-en-US-18.0-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-logrotate-3.8.2-2.centos.7+p18.0.31.0+t200923.1454.x86_64
psa-passwd-5.0.7-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-mnemo-4.2.14-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-autoinstaller-3.30.0-1centos.7.200825.1144.x86_64
psa-turba-4.2.21-cos7.build1708180425.15.noarch
psa-ingo-3.2.16-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-mail-driver-common-17.8.11-cos7.build1708200321.09.x86_64
psa-17.8.11-cos7.build1708180301.19.x86_64
psa-mod_fcgid-2.3.9.5-2.centos.7+p18.0.30.2+t200930.1355.x86_64
psa-libxml-proxy-2.9.7-2.centos.7+p18.0.31.0+t200923.1454.x86_64
psa-ingo-3.2.16-cos7.build1708180425.15.noarch
psa-phpmyadmin-4.9.0.1-cos7.build1708190626.13.noarch
psa-mod_aclr2-14081815-2.centos.7+p18.0.27.0+t200424.1018.x86_64
psa-kronolith-4.2.29-2.centos.7+p18.0.30.2+t200930.1355.noarch
psa-php5-configurator-1.8.0-2.centos.7+p18.0.30.2+t200930.1355.x86_64
psa-selinux-18.0.10-2.centos.7+p18.0.30.2+t200930.1355.noarch
 

Attachments

  • plesk installation log.zip
    4.8 KB · Views: 2
Last edited:
According to the log several Obisidian libraries were already installed when the update was attempted. This does not look like the log from the first upgrade attempt, but as if an unsuccessful attempt was made previously. Hard to tell what the right action from here could be.

I'd try
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
and then
# plesk repair installation
and see how that goes.

You do have a backup, don't you? In that case it could be even better to reinstall the whole system with the latest Plesk version and then restore your backup to the new version.
 
You are right, there are 2-3 logs of myself attempting to install, I may have mixed this within my thread, sorry.

I am looking at reinstalling the server now and I'm happy to see something listed!
  • Plesk Obsidian (Unlimited Domains) (Free)
I am extremely inexperienced with the server-side of things, I have been getty by with help here and there. When Plesk did not install, I somewhat panicked and simply tried again, then Plesk lost its styling and I was struggling to do anything.
 
Back
Top