• 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 Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

L

LarsK

New Pleskian
I am currently running RC4, while using the autoinstaller to update to the RTM release I get the following error:


Code: 
Loaded plugins: fastestmirror, rhnplugin
This system is receiving updates from CLN.
Loading mirror speeds from cached hostfile
 * epel: mirror.nl.leaseweb.net
PHP_7_1-thirdparty                                       | 2.9 kB     00:00
PHP_7_2-thirdparty                                       | 2.9 kB     00:00
PHP_7_3-thirdparty                                       | 2.9 kB     00:00
PLESK_17_PHP71                                           | 2.9 kB     00:00
PLESK_17_PHP72                                           | 2.9 kB     00:00
PLESK_17_PHP73                                           | 2.9 kB     00:00
PLESK_18_0_19-dist                                       | 2.9 kB     00:00
PLESK_18_0_19-extras                                     | 2.9 kB     00:00
PLESK_18_0_19-thirdparty                                 | 2.9 kB     00:00
Attempt to remove 'psa-pylibplesk' to resolve conflict has succeeded
Attempt to remove 'plesk-ext-rest-api' to resolve conflict has succeeded
Attempt to remove 'plesk-skins' to resolve conflict has succeeded
Attempt to remove 'plesk-ext-catalog' to resolve conflict has succeeded
Attempt to remove 'plesk-base' to resolve conflict has succeeded
Exception: Failed to solve dependencies:
plesk-dovecot-pigeonhole-0.5.7.2-centos7.19090322.x86_64 requires plesk-dovecot-abi-2.3.abiv7

ERROR: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.
 
I can't, our license was supplied by TransIP. I contacted them but it's pretty useless that i have to contact them and they just pass on the question to Plesk support.
Is there any way that I could contact plesk support directly?
 
fferraro87 said:
i've same problem, i don't know how can i do this
Click to expand...
Kingsley said:
I have the same problem here, can't update to 18.0.19/.1 this is strange
Click to expand...

Hello,

The issue was not reproduced in the test environment. The update was finished without any issues.

For further investigation SSH access to the server is required.

To provide us with server access you may use Support SSH Access extension:
How to provide Plesk Support Team with the SSH access to the server?

Looking forward to your reply.
Best Regards,
Vladimir Chernikov
Technical Support
Plesk
Click to expand...

I just got a reply from my service provider (TransIP). They contacted Plesk support for me. Plesk support can't replicate out problem on their test systems so they need SSH access to my server, which is a problem for me.

Is one of you able to contact Plesk support and give them SSH access to one of your servers?

Anthony said:
I recommend contacting our support Plesk Help Center
Click to expand...
Are you able to relay this issue to support for me, as I have trouble contacting Plesk support directly.
As 2 people also have the same problem this doesn't seem to be an isolated case.
 
LarsK said:
I just got a reply from my service provider (TransIP). They contacted Plesk support for me. Plesk support can't replicate out problem on their test systems so they need SSH access to my server, which is a problem for me.

Is one of you able to contact Plesk support and give them SSH access to one of your servers?


Are you able to relay this issue to support for me, as I have trouble contacting Plesk support directly.
As 2 people also have the same problem this doesn't seem to be an isolated case.
Click to expand...
i've open a ticket right now to plesk help center
 
Hi, @LarsK

LarsK said:
Are you able to relay this issue to support for me, as I have trouble contacting Plesk support directly.
Click to expand...

Please try the steps provided by IgorG.

I'm from the Plesk engineering team, and I personally can't replicate the issue about w/o non-available update on Plesk Obsidian preview servers. I successfully updated a couple of my own. The logic for Plesk Obsidian preview servers is the following:
- All of them have 'Early Adopters' tier by default. It means they should see a new release w/o delays.
- Plesk server checks new updates on a daily basis. Here could be a delay up to 24 hours (but usually fewer). To trigger this, you can manually run in SSH 'plesk daily'.
- Also you can try # plesk installer --all-versions

All these conditions should be enough to update to the RTM build.

I can assume that in your case we could have issues with repository mirrors - they need some time to replicate changes from Plesk official repository.
 
Anthony said:
Hi, @LarsK



Please try the steps provided by IgorG.

I'm from the Plesk engineering team, and I personally can't replicate the issue about w/o non-available update on Plesk Obsidian preview servers. I successfully updated a couple of my own. The logic for Plesk Obsidian preview servers is the following:
- All of them have 'Early Adopters' tier by default. It means they should see a new release w/o delays.
- Plesk server checks new updates on a daily basis. Here could be a delay up to 24 hours (but usually fewer). To trigger this, you can manually run in SSH 'plesk daily'.
- Also you can try # plesk installer --all-versions

All these conditions should be enough to update to the RTM build.

I can assume that in your case we could have issues with repository mirrors - they need some time to replicate changes from Plesk official repository.
Click to expand...

Running plesk daily gives me the following errors:

Code: 
[
root@titan ~]# plesk daily
[2019-09-27 08:47:32.419] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/f2bmng' '--get-stats'] with exit code [1]
[2019-09-27 08:47:32.422] ERR [panel] f2bmng failed: ERROR:__main__:Failed to get packages by files: package manager returned 24 lines instead of expected 17
[2019-09-27 08:47:39.732] ERR [panel] Failed to read X509 certificate from PEM string: error:0D07209B:asn1 encoding routines:ASN1_get_object:too long

Running "plesk installer --all-versions" to install 18.0.19 is what got me the error in the first place. It seems that i get past the previous error, but now i got this one:
Code: 
Installing packages
Loaded plugins: fastestmirror, rhnplugin
This system is receiving updates from CLN.
Loading mirror speeds from cached hostfile
 * cloudlinux-x86_64-server-7: cl-mirror.vimexx.nl
 * epel: ftp.nluug.nl
pp18.0.19-bootstrapper-18.0-2.centos.7+p18.0.19.2+t19092 | 179 kB     00:00
Running Transaction Check
Installing: pp18.0.19-bootstrapper-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64 [1/1]
Verify: 1/1: pp18.0.19-bootstrapper.x86_64 0:18.0-2.centos.7+p18.0.19.2+t190926.1641 - u
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp18.0.19-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
Loaded plugins: fastestmirror, rhnplugin
This system is receiving updates from CLN.
Loading mirror speeds from cached hostfile
 * cloudlinux-x86_64-server-7: cl-mirror.vimexx.nl
 * epel: ftp.nluug.nl
Package pp18.0.19-bootstrapper-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64 already installed and latest version
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
mod_security-2.9.3-2.centos.7+p18.0.19.2+t190926.1641.x8 | 270 kB     00:00
fail2ban-0.10.3.1-2.centos.7+p18.0.19.2+t190926.1641.noa | 581 kB     00:00
plesk-completion-18.0-2.centos.7+p18.0.19.2+t190926.1641 | 821 kB     00:00
plesk-backup-utilities-18.0-2.centos.7+p18.0.19.2+t19092 | 3.4 MB     00:00
plesk-config-troubleshooter-18.0-2.centos.7+p18.0.19.2+t | 1.1 MB     00:00
plesk-control-panel-18.0-2.centos.7+p18.0.19.2+t190926.1 | 4.8 MB     00:00
plesk-core-utilities-18.0-2.centos.7+p18.0.19.2+t190926. | 872 kB     00:00
plesk-dns-bind-driver-18.0-2.centos.7+p18.0.19.2+t190926 | 439 kB     00:00
plesk-dovecot-2.3.7.2-2.centos.7+p18.0.19.2+t190926.1641 | 986 kB     00:00
plesk-dovecot-core-2.3.7.2-2.centos.7+p18.0.19.2+t190926 | 2.7 MB     00:00
plesk-dovecot-imap-driver-18.0-2.centos.7+p18.0.19.2+t19 | 417 kB     00:00
plesk-dovecot-pigeonhole-0.5.7.2-2.centos.7+p18.0.19.2+t | 614 kB     00:00
plesk-fail2ban-configurator-18.0-2.centos.7+p18.0.19.2+t | 203 kB     00:00
plesk-core-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_6 |  27 MB     00:01
plesk-mail-pc-driver-18.0-2.centos.7+p18.0.19.2+t190926. | 1.6 MB     00:00
plesk-management-node-18.0-2.centos.7+p18.0.19.2+t190926 |  73 kB     00:00
plesk-modsecurity-configurator-18.0-2.centos.7+p18.0.19. | 407 kB     00:00
plesk-modsecurity-crs-18.0-2.centos.7+p18.0.19.2+t190926 | 172 kB     00:00
plesk-release-18.0.19.2-2.centos.7+p18.0.19.2+t190926.19 | 2.8 kB     00:00
plesk-l10n-18.0-2.centos.7+p18.0.19.2+t190926.1641.noarc | 8.2 MB     00:00
plesk-repair-kit-18.0-2.centos.7+p18.0.19.2+t190926.1916 | 3.5 MB     00:00
plesk-roundcube-1.3.9-2.centos.7+p18.0.19.2+t190926.1641 | 4.1 MB     00:00
plesk-ui-library-18.0-2.centos.7+p18.0.19.2+t190926.1916 | 2.1 MB     00:00
plesk-web-hosting-18.0-2.centos.7+p18.0.19.2+t190926.164 | 140 kB     00:00
plesk-service-node-utilities-18.0-2.centos.7+p18.0.19.2+ | 3.2 MB     00:00
plesk-web-socket-18.0-2.centos.7+p18.0.19.2+t190926.1641 | 104 kB     00:00
psa-18.0.19-2.centos.7+p18.0.19.2+t190926.1641.x86_64.rp | 134 kB     00:00
psa-firewall-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86 | 1.0 MB     00:00
psa-autoinstaller-3.23.19-1centos.7.190912.1532.x86_64.r | 5.5 MB     00:00
psa-imp-6.2.21.1-2.centos.7+p18.0.19.2+t190926.1641.noar | 2.5 MB     00:00
psa-ingo-3.2.16-2.centos.7+p18.0.19.2+t190926.1641.noarc | 880 kB     00:00
psa-kronolith-4.2.23-2.centos.7+p18.0.19.2+t190926.1641. | 1.4 MB     00:00
psa-libpam-plesk-18.0-2.centos.7+p18.0.19.2+t190926.1641 | 490 kB     00:00
psa-locale-base-en-US-18.0-2.centos.7+p18.0.19.2+t190926 | 363 kB     00:00
psa-mail-driver-common-18.0-2.centos.7+p18.0.19.2+t19092 | 1.2 MB     00:00
psa-horde-5.2.17-2.centos.7+p18.0.19.2+t190926.1641.noar |  13 MB     00:01
psa-mnemo-4.2.14-2.centos.7+p18.0.19.2+t190926.1641.noar | 714 kB     00:00
psa-mod_proxy-2.4.6-2.centos.7+p18.0.19.2+t190926.1641.x | 160 kB     00:00
psa-php5-configurator-1.8.0-2.centos.7+p18.0.19.2+t19092 |  69 kB     00:00
psa-passwd-5.0.7-2.centos.7+p18.0.19.2+t190926.1641.noar | 673 kB     00:00
psa-proftpd-1.3.6-2.centos.7+p18.0.19.2+t190926.1641.x86 | 2.1 MB     00:00
psa-spamassassin-18.0-2.centos.7+p18.0.19.2+t190926.1641 | 227 kB     00:00
psa-turba-4.2.21-2.centos.7+p18.0.19.2+t190926.1641.noar | 1.1 MB     00:00
psa-vhost-18.0-2.centos.7+p18.0.19.2+t190926.1641.noarch | 255 kB     00:00
psa-phpmyadmin-4.9.0.1-2.centos.7+p18.0.19.2+t190926.164 | 6.1 MB     00:01
psa-watchdog-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86 | 2.2 MB     00:00
sw-collectd-5.8.1-2.centos.7+p18.0.19.2+t190926.1641.x86 | 547 kB     00:00
sw-nginx-1.16.1.3-2.centos.7+p18.0.19.2+t190926.1641.x86 | 5.0 MB     00:00
Running Transaction Check
Fatal error during packages installation: [u'ERROR with transaction check vs depsolve:', 'psa-libxml-proxy is needed by plesk-backup-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64', 'psa-logrotate is needed by plesk-service-node-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64']
YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'psa-libxml-proxy is needed by plesk-backup-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64', 'psa-logrotate is needed by plesk-service-node-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64']

ERROR: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.
exit status 1
[root@titan ~]#

Running Yum update now, it seems to have a lot of packages to update and install so i'll try the installation again after the yum update
 
Nope, still the exact same error:
Running Transaction Check
Fatal error during packages installation: [u'ERROR with transaction check vs depsolve:', 'psa-libxml-proxy is needed by plesk-backup-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64', 'psa-logrotate is needed by plesk-service-node-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64']
YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'psa-libxml-proxy is needed by plesk-backup-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64', 'psa-logrotate is needed by plesk-service-node-utilities-18.0-2.centos.7+p18.0.19.2+t190926.1641.x86_64']

ERROR: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Visit Plesk Help Center to search for a solution.
exit status 1
Click to expand...

What is do notice is that the first time I ran it it said that there is 1 package required for the product to function properly. After the yum update is says:

Code: 
Preparing Your System for Product Installation
===============================================================================

There are 0 packages required for the product to function properly which
were not found in your system.

There are 48 packages that need to be upgraded
in order to install the product.

There are 9 packages that are installed, but will be removed.


Available actions:
(F) Go forward
(B) Go back
(Q) Cancel installation
(S) Show the list of packages

Select an action [F/b/q/s]: f
 
hey there, when I'm trying to update latest build getting error also stuck in 43/150 on update stage what should I do? also server gives me plesk 500 error when I'm trying to sign-in to my server, how do I continue installation process?
 
Last edited:
selcukedirne said:
hey there, when I'm trying to update latest build getting error also stuck in 43/150 on update stage what should I do? also server gives me plesk 500 error when I'm trying to sign-in to my server, how do I continue installation process?
Click to expand...

Please create your own thread instead of hijacking mine, i do not have the same problem and i do not have an answer for you.

Regarding to my issue, still not fixed.
 
@LarsK,

LarsK said:
I contacted them but it's pretty useless that i have to contact them and they just pass on the question to Plesk support.
Click to expand...
I still recommend using this way, as we can't fix the issue based on logs. We need access to the server to define what could be wrong with packages dependencies and how to fix it permanently, not just fix symptoms.
 
You must log in or register to reply here.

Similar threads

Matt N
Resolved 18.0.40 upgrade killed postfix, now no mail
Replies
8
Views
2K
Matt N
Matt N
agarzon
Resolved Error updating from CLI
Replies
2
Views
2K
selcukedirne
selcukedirne
bokishaNET
Resolved Some errors occured during installation Plesk Obsidian Version 18.0.26
Replies
7
Views
5K
bokishaNET
bokishaNET
R
Issue Software inoperable after update fail
Replies
4
Views
2K
ggorg
G
Shiv
Resolved Some errors occured during update installation.
Replies
9
Views
2K
Shiv
Shiv
Back
Top