• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Problem update plesk

Nicola

Basic Pleskian
Hi,
I'm tryng to install the last update for plesk, but I get this error:

umRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'mariadb-server >= 5.0.60 is needed by plesk-mysql-server-18.0.1-2.centos.7+p18.0.43.0+t220331.2159.noarch']
Lancio dei checker di componenti e prodotto in corso...

Current version:
- Versione Plesk Obsidia 18.0.42 #1
- OS Centos 7
- Mysql 5.7
Update to: Plesk Obsidian 18.0.43

What can I do?

Thanks
 

Attachments

  • plesk-installation-log.zip
    3.5 KB · Views: 0
Hello,

It's known problem of Plesk 18.0.43 with ID PPPM-13514 - update to 18.0.43 failed if MySQL community server was installed on server. Expect fix in 18.0.43 #1
 
Hi,

how to give plesk the info to use "18.0.43 Update 1" ?
When trying to update the panel, the problem described still remains


Code:
Fatal error during packages installation: [u'ERROR with transaction check vs depsolve:', 'mariadb-server >= 5.0.60 is needed by plesk-mysql-server-18.0.1-2.centos.7+p18.0.43.0+t220331.2159.noarch']
YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'mariadb-server >= 5.0.60 is needed by plesk-mysql-server-18.0.1-2.centos.7+p18.0.43.0+t220331.2159.noarch']
 
Did you try to run the update from the command-line?

Code:
# plesk installer update
Yes, of course. But using the cli command does not present a newer version:

Code:
# plesk installer update
You already have the latest version of product(s) and all the selected components installed. Installation will not continue.

Code:
# plesk installer upgrade
Detecting installed product components.
--- prod_id  release_id           (description)                            (tiers) ---
plesk        PLESK_18_0_43        (Plesk Obsidian 18.0.43)                 (stable)
plesk        PLESK_18_0_42        (Plesk Obsidian 18.0.42)                 (currently installed)


The GUI:
1650127932602.png

And the web installer:
1650127785455.png
 
# plesk installer upgrade 18.0.43

If I issue the command, the error is always the same:
Fatal error during packages installation: [u'ERROR with transaction check vs depsolve:', 'mariadb-server >= 5.0.60 is needed by plesk-mysql-server-18.0.1-2.centos.7+p18.0.43.0+t220331.2159.noarch']
YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'mariadb-server >= 5.0.60 is needed by plesk-mysql-server-18.0.1-2.centos.7+p18.0.43.0+t220331.2159.noarch']
 
Hello,

Could you post /var/log/plesk/install/autoinstaller3.log fragment if `plesk installer upgrade 18.0.43 --debug` is running? If it doesn't possible, please answer of following questions:
* Do you have some custom repo configured - is SOURCE present in /root/.autoinstallerrc and autoinstall.plesk.com is resolves to some cdn77 hosts?
* What MySQL packages are installed: rpm -qa | grep -i 'mariadb\|mysql'
 
I attach the file autoinstaller3.log

There are 2 files in the folder "/root/.autoinstaller/": microupdates.xml and options.ini (empty).

The content of microupdates.xml is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<patches>
<product id="plesk" version="18.0.27" installed-at="20200512T133815" />
</patches>

autoinstall.plesk.com resolves to some cdn77 hosts.


rpm -qa | grep -i 'mariadb\|mysql':
mysql-community-libs-5.7.37-1.el7.x86_64
plesk-libmariadbclient-3.0-3.0.9-1centos.7.200430.1921.x86_64
plesk-php71-mysql-7.1.33-1centos.7.211108.1944.x86_64
plesk-php55-mysql-5.5.38-centos7.17090117.x86_64
mysql-community-libs-compat-5.7.37-1.el7.x86_64
plesk-libmariadbclient-3.1-3.1.8-1centos.7.200603.1842.x86_64
mysql-community-server-5.7.37-1.el7.x86_64
mysql57-community-release-el7-11.noarch
plesk-libmariadbclient-1.0-1.0.0-0centos.7.171006.1040.x86_64
plesk-mysql-connector-odbc-5.2.7-centos7.17091819.x86_64
php-mysql-5.4.45-56.el7.art.x86_64
plesk-php80-mysql-8.0.18-1centos.7.220415.1034.x86_64
mysql-community-client-5.7.37-1.el7.x86_64
plesk-php56-mysql-5.6.40-centos7.21111012.x86_64
plesk-php81-mysql-8.1.5-1centos.7.220415.1034.x86_64
plesk-php73-mysql-7.3.33-1centos.7.211118.1928.x86_64
plesk-php72-mysql-7.2.34-1centos.7.211108.1944.x86_64
plesk-php74-mysql-7.4.29-1centos.7.220415.1034.x86_64
mysql-community-common-5.7.37-1.el7.x86_64
plesk-mysql-server-18.0-2.centos.7+p18.0.17.0+t190721.1104.noarch
plesk-php70-mysql-7.0.33-centos7.21110918.x86_64
perl-DBD-MySQL-4.023-6.el7.x86_64
 

Attachments

  • autoinstaller3.zip
    67.1 KB · Views: 0
I'm worried about doing this because it's a production server, does doing this mean having to reinstall mysql? I've never used maria-db, can't I delete mariadb-server packages?

yum list installed | grep mariadb
plesk-libmariadbclient-1.0.x86_64
plesk-libmariadbclient-3.0.x86_64
plesk-libmariadbclient-3.1.x86_64
 
Hello,

> I'm worried about doing this because it's a production server, does doing this mean having to reinstall mysql?
No, plesk-mysql-server and plesk-mysql-server-community are dependency packages, and installation of plesk-mysql-server-community just keeps the package system consistent because mariadb-server and mysql-server-community has different provides

> I've never used maria-db, can't I delete mariadb-server packages?
plesk-libmariadbclient pakcage are just client libraries which are used by Plesk to connect to MySQL server, so it doesn't affect your server installation
 
Back
Top