• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Plesk Version 12.5.30 upgrade to 17.8.11 failed

Goncharenko

New Pleskian
Hello there!
  1. Several days ago I've run upgrade of Plesk from version 12.5.30 to 17.8.11 via GUI interface. This upgrade was failed, because we haven't free space (I found this issue later - my mistake). After space clean (now we have 17GB free space) I am trying to run upgrade once again, but received below issues:

  • via GUI interface I see message '"Upgrade to Plesk 17.8.11 is available", but after clicking on this message I see that this update "was installed" and no other updates is available
    Screenshot 2021-03-30 122024.jpg
  • I checked version from ssh and it's looks like we have "old" version 12.5.30
Product version: Plesk Onyx 12.5.30
Build date: 2018/12/14 14:00
OS version: Ubuntu 14.04
Revision: c3fb546fb867ac424d65da14d8b023f11ec0d150
Architecture: 64-bit
Wrapper version: 1.2
  • next step: plesk installer update
"You already have the latest version of product(s) and all the selected components
installed. Installation will not continue."
  • next step: plesk installer --select-release-latest --upgrade-installed-components
"You already have the latest version of product(s) and all the selected components
installed. Installation will not continue."
  • next step: plesk installer --select-release-latest --reinstall-patch --upgrade-installed-components
"All patches were applied.
Patches were installed successfully.
The changes were applied successfully."

I checked version from ssh and it was the same "old" version 12.5.30!
  • next step: plesk repair installation
"
Bootstrapper repair finished.
Errors occurred while performing the following actions: restore mail, fix Apache configuration.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

exit status 1"

And again nothing is changed. You can see error messages below. Maybe someone can help me to upgrade Plesk.
Thank you!

...

WARNING:Skip fixing 'psa-autoinstaller': Cannot find deb-archive for package psa-autoinstaller (3.22.14-ubuntu.14.04.190117.1649)
WARNING:Skip fixing 'psa-drweb-configurator': Cannot find deb-archive for package psa-drweb-configurator (17.8.11-ubuntu14.04.build1708180301.19)
WARNING:Skip fixing 'psa-firewall': Cannot find deb-archive for package psa-firewall (17.8.11-ubuntu14.04.build1708180301.19)
WARNING:Skip fixing 'psa-kav8': Cannot find deb-archive for package psa-kav8 (1:8.5.1-ubuntu14.04.19041014)
WARNING:Skip fixing 'psa-libxml-proxy': Cannot find deb-archive for package psa-libxml-proxy (2.9.7-ubuntu14.04.18021314)
WARNING:Skip fixing 'psa-locale-base-en-us': Cannot find deb-archive for package psa-locale-base-en-us (17.8.11-ubuntu14.04.build1708190409.21)
WARNING:Skip fixing 'psa-logrotate': Cannot find deb-archive for package psa-logrotate (3.8.2-ubuntu14.04.build1708171004.18)
WARNING:Skip fixing 'psa-mail-driver-common': Cannot find deb-archive for package psa-mail-driver-common (17.8.11-ubuntu14.04.build1708190416.19)
WARNING:Skip fixing 'psa-pear': Cannot find deb-archive for package psa-pear (1.10.5-20180124.ubuntu14.04.18012417)
WARNING:Skip fixing 'psa-php5-configurator': Cannot find deb-archive for package psa-php5-configurator (1.7.0-ubuntu14.04.build1708180212.17)
WARNING:Skip fixing 'psa-phpfpm-configurator': Cannot find deb-archive for package psa-phpfpm-configurator (1.0.0-ubuntu14.04.build1708180212.17)
WARNING:Skip fixing 'psa-phpmyadmin': Cannot find deb-archive for package psa-phpmyadmin (4.8.4-ubuntu14.04.build1708181212.18)
WARNING:Skip fixing 'psa-pylibplesk': Cannot find deb-archive for package psa-pylibplesk (17.8.11-ubuntu14.04.build1708180301.19)
WARNING:Skip fixing 'psa-spamassassin': Cannot find deb-archive for package psa-spamassassin (17.8.11-ubuntu14.04.build1708180301.19)
WARNING:Skip fixing 'psa-vhost': Cannot find deb-archive for package psa-vhost (17.8.11-ubuntu14.04.build1708180425.13)
WARNING:Skip fixing 'psa-watchdog': Cannot find deb-archive for package psa-watchdog (17.8.11-ubuntu14.04.build1708190221.14)
WARNING:Skip fixing 'sw-collectd': Cannot find deb-archive for package sw-collectd (5.5.0.1-ubuntu14.04.18012210)
WARNING:Skip fixing 'sw-cp-server': Cannot find deb-archive for package sw-cp-server (2.5.1-ubuntu14.04.18012916)
WARNING:Skip fixing 'sw-doctrine': Cannot find deb-archive for package sw-doctrine (1.0.4-0.280352)
WARNING:Skip fixing 'sw-engine': Cannot find deb-archive for package sw-engine (2.24.12-ubuntu.14.04.190212.1352)
WARNING:Skip fixing 'sw-engine-cli-2.16': Cannot find deb-archive for package sw-engine-cli-2.16 (2.16.2-ubuntu1404.201510051442)
WARNING:Skip fixing 'sw-engine-cli-2.24': Cannot find deb-archive for package sw-engine-cli-2.24 (2.24.12-ubuntu.14.04.190212.1352)
WARNING:Skip fixing 'sw-libboost-date-time1.54.0': Cannot find deb-archive for package sw-libboost-date-time1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-date-time1.55.0': Cannot find deb-archive for package sw-libboost-date-time1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-filesystem1.54.0': Cannot find deb-archive for package sw-libboost-filesystem1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-filesystem1.55.0': Cannot find deb-archive for package sw-libboost-filesystem1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-iostreams1.55.0': Cannot find deb-archive for package sw-libboost-iostreams1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-program-options1.54.0': Cannot find deb-archive for package sw-libboost-program-options1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-program-options1.55.0': Cannot find deb-archive for package sw-libboost-program-options1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-regex1.54.0': Cannot find deb-archive for package sw-libboost-regex1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-regex1.55.0': Cannot find deb-archive for package sw-libboost-regex1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-serialization1.54.0': Cannot find deb-archive for package sw-libboost-serialization1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-serialization1.55.0': Cannot find deb-archive for package sw-libboost-serialization1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-system1.54.0': Cannot find deb-archive for package sw-libboost-system1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-system1.55.0': Cannot find deb-archive for package sw-libboost-system1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libboost-thread1.54.0': Cannot find deb-archive for package sw-libboost-thread1.54.0 (1.54.0-14060316)
WARNING:Skip fixing 'sw-libboost-thread1.55.0': Cannot find deb-archive for package sw-libboost-thread1.55.0 (1.55.0-ubuntu14.04.14070416)
WARNING:Skip fixing 'sw-libmilter': Cannot find deb-archive for package sw-libmilter (8.14.5-14060221)
WARNING:Skip fixing 'sw-libpoco': Cannot find deb-archive for package sw-libpoco (1.4.3p1.1-ubuntu14.04.14101519)
WARNING:Skip fixing 'sw-librrd': Cannot find deb-archive for package sw-librrd (1.6.0.1-ubuntu14.04.18012210)
WARNING:Skip fixing 'sw-rrdtool': Cannot find deb-archive for package sw-rrdtool (1.6.0.1-ubuntu14.04.18012210)
WARNING:Skip fixing 'sw-tar': Cannot find deb-archive for package sw-tar (1.29-2.ubuntu14.04.17051015)
WARNING:Skip fixing 'wpb-core': Cannot find deb-archive for package wpb-core (17.8.12-43703.18032617)
WARNING:Skip fixing 'wpb-designs-00': Cannot find deb-archive for package wpb-designs-00 (17.8.12-43703.18032616)
WARNING:Skip fixing 'wpb-designs-01': Cannot find deb-archive for package wpb-designs-01 (17.8.12-43703.18032616)
WARNING:Skip fixing 'wpb-designs-03': Cannot find deb-archive for package wpb-designs-03 (17.8.12-43703.18032616)
WARNING:Skip fixing 'wpb-designs-04': Cannot find deb-archive for package wpb-designs-04 (17.8.12-43703.18032616)
WARNING:Skip fixing 'wpb-designs-05': Cannot find deb-archive for package wpb-designs-05 (17.8.12-43703.18032616)
WARNING:Skip fixing 'wpb-designs-07': Cannot find deb-archive for package wpb-designs-07 (17.8.12-43703.18032616)
WARNING:Skip fixing 'wpb-designs-09': Cannot find deb-archive for package wpb-designs-09 (17.8.12-43703.18032617)
WARNING:Skip fixing 'wpb-designs-12': Cannot find deb-archive for package wpb-designs-12 (17.8.12-43703.18032617)
WARNING:Skip fixing 'wpb-designs-14': Cannot find deb-archive for package wpb-designs-14 (17.8.12-43703.18032617)
WARNING:Skip fixing 'wpb-designs-20': Cannot find deb-archive for package wpb-designs-20 (17.8.12-43703.18032617)
WARNING:Skip fixing 'wpb-headers': Cannot find deb-archive for package wpb-headers (17.8.12-43703.18032617)

Bootstrapper repair finished.
Errors occurred while performing the following actions: restore mail, fix Apache configuration.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.
 
"If you can't resolve the issue on your own, please address Plesk support."
There is no easy fix you can do on your own.
 
"If you can't resolve the issue on your own, please address Plesk support."
There is no easy fix you can do on your own.

I can't address it to Plesk support, because my license was purchased not directly from Plesk (you can see this message on the screenshot below).
Do you have other ideas how I can fix this issue?
Thank you in advance!

Screenshot 2021-04-01 143059.jpg
 
You have a 30-day money-back-guarantee. Personally, I think that Plesk support is worth every single Cent you spend on it, but if you just want to test it for one case, that'll be o.k. It's your decision. But this won't be the last technical problem you can experience with a server, so if you you are unsure, I think it is well invested money.
 
Back
Top