Resolved Plesk Update from 12.5 to Onyx fails.

[Arsi Koutaniemi]

On my server automatic update keeps failing

It complains following on the log file...

Execution failed.
Command: autoinstaller
Arguments: Array
(
[0] => --select-product-id
[1] => plesk
[2] => --select-release-current
[3] => --upgrade-installed-components
)

Details: Doing restart of Plesk Installer...
Detecting installed product components.
Retrieving information about the installed license key...
Launching component checkers...
.
.
.
Lot of successful downloads here
.
.
.
Downloading file PSA_12.5.30/examiners/panel_preupgrade_checker.php: 0%
| 424 kB 00:00
Loading mirror speeds from cached hostfile
* base: mirror.wiuwiu.de
* epel: mirror.wiuwiu.de
* extras: mirror.wiuwiu.de
* updates: mirror.fra10.de.leaseweb.net
* webtatic: uk.repo.webtatic.com
Attempt to remove 'php56w-common' to resolve conflict has succeeded
Exception: Failed to solve dependencies:
psa-phpfpm-configurator-1.0.0-cos7.build1205160218.11.x86_64 requires psa-php5-configurator

ERROR: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please contact product technical support.

 

[IgorG]

What is the output of the command:

# rpm -qa | grep psa-php5

Run command:

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

and try to run upgrade again.

 

[trialotto]

@Arsi Koutaniemi

I would rather recommend that you take some steps in the upgrade process and (in chronological order)

1 - upgrade from Plesk 12.5.30 to Plesk 17.0.17
2 - upgrade from Plesk 17.0.17 to Plesk 17.5.3 or 17.8.11 (latest version is recommended)

in order to

- prevent that huge differences in packages can create severe issues
- issues can be identified and resolved on a step-by-step basis

and the above is only a rough outline of the advantages of doing a staged upgrade process.

Also note that your package repos are a bit "odd", in the sense that the list of repos

* base: mirror.wiuwiu.de
* epel: mirror.wiuwiu.de
* extras: mirror.wiuwiu.de
* updates: mirror.fra10.de.leaseweb.net
* webtatic: uk.repo.webtatic.com

is indicating that you have a number of non-standard repos: this is very likely to be the root cause of the problem, if and only if those repos are not properly updated and/or properly configured.

I am not sure whether you own the wiuwiu.de domain and/or whether you maintain your own repo.

However, I am pretty sure that you should not use the mirrors from wiuwiu.de.

In short, selecting proper repo mirrors would probably do the trick and relieve most or all of your current problems.

Kind regards......

 

[Arsi Koutaniemi]

What is the output of the command:

# rpm -qa | grep psa-php5

Run command:

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

and try to run upgrade again.

rpm -qa gives

psa-php5-configurator-1.7.0-cos7.build1205150924.14.x86_64

Running command plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
fails with error

Exception: Failed to solve dependencies:
psa-phpfpm-configurator-1.0.0-cos7.build1205160218.11.x86_64 requires psa-php5-configurator

 

[Arsi Koutaniemi]

@Arsi Koutaniemi

I would rather recommend that you take some steps in the upgrade process and (in chronological order)

1 - upgrade from Plesk 12.5.30 to Plesk 17.0.17
2 - upgrade from Plesk 17.0.17 to Plesk 17.5.3 or 17.8.11 (latest version is recommended)

in order to

- prevent that huge differences in packages can create severe issues
- issues can be identified and resolved on a step-by-step basis

and the above is only a rough outline of the advantages of doing a staged upgrade process.

Also note that your package repos are a bit "odd", in the sense that the list of repos

* base: mirror.wiuwiu.de
* epel: mirror.wiuwiu.de
* extras: mirror.wiuwiu.de
* updates: mirror.fra10.de.leaseweb.net
* webtatic: uk.repo.webtatic.com

is indicating that you have a number of non-standard repos: this is very likely to be the root cause of the problem, if and only if those repos are not properly updated and/or properly configured.

I am not sure whether you own the wiuwiu.de domain and/or whether you maintain your own repo.

However, I am pretty sure that you should not use the mirrors from wiuwiu.de.

In short, selecting proper repo mirrors would probably do the trick and relieve most or all of your current problems.

Kind regards......

wiuwiud.de is repo for Centos.

Plesk comes from

Repo-id : plesk-migrator
Repo-name : Plesk packages for migrator
Repo-status : enabled
Repo-revision: 1443588075
Repo-updated : Wed Sep 30 06:41:18 2015
Repo-pkgs : 9
Repo-size : 13 M
Repo-baseurl : http://autoinstall.plesk.com/PMM_0.1.10/dist-rpm-CentOS-7-x86_64/
Repo-expire : 21,600 second(s) (last: Mon Dec 3 08:14:37 2018)
Filter : read-onlyresent
Repo-filename: /etc/yum.repos.d/plesk-migrator.repo

Repo-id : plesk-migrator-tp
Repo-name : Plesk 3d-party packages for migrator
Repo-status : enabled
Repo-revision: 1443588078
Repo-updated : Wed Sep 30 06:41:19 2015
Repo-pkgs : 0
Repo-size : 0
Repo-baseurl : http://autoinstall.plesk.com/PMM_0.1.10/thirdparty-rpm-CentOS-7-x86_64/
Repo-expire : 21,600 second(s) (last: Mon Dec 3 08:14:37 2018)
Filter : read-onlyresent
Repo-filename: /etc/yum.repos.d/plesk-migrator.repo


Regards,

Arsi

 

[trialotto]

@Arsi Koutaniemi

I noticed that wiuwiu is a CentOS mirror...........but it is rather obscure AND it is rather odd that you have

updates: mirror.fra10.de.leaseweb.net

while using wiuwiu.de for the main packages.

In short, no surprise here: it can be expected that you will not have any problems when changing the (main) mirrors to mirror.fra10.de.leaseweb.net.

That already was the nature of an earlier response of my side.

Regards........