• 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

Issue Upgrade from MySQL 5.5 to 5.6 (CentOS 6.10)

E-ffective

New Pleskian
Hi all,

I am attempting to update MySQL on my Plesk server from 5.5 to 5.6. I have followed the guide here and initially run into the problem outlined here. Unfortunately the latter does not seem to have resolved the issue, in trying to update to 5.6.

Can anyone of you kind people please suggest a solution? Do I need to update the 'php-mysql' package, as well as the 'mysql' package, for example?

Error Output
Error: Package: php-mysql-5.4.45-14.el6.remi.x86_64 (@Remi)
Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Removing: mysql-libs-5.5.60-1.el6.remi.x86_64 (@Remi)
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Obsoleted By: mysql-community-libs-5.6.40-2.el6.x86_64 (mysql56-community)
Not found​
Full Output
yum update mysql
Loaded plugins: fastestmirror
Setting up Update Process
Loading mirror speeds from cached hostfile
epel/metalink | 32 kB 00:00
* epel: ftp.uni-stuttgart.de
* remi-safe: mirror.23media.de
CityFan | 2.9 kB 00:00
PLESK_17_8_11-extras | 2.9 kB 00:00
PLESK_17_PHP52 | 2.9 kB 00:00
PLESK_17_PHP53 | 2.9 kB 00:00
PLESK_17_PHP54 | 2.9 kB 00:00
PLESK_17_PHP55 | 2.9 kB 00:00
PLESK_17_PHP56 | 2.9 kB 00:00
PLESK_17_PHP70 | 2.9 kB 00:00
base | 3.7 kB 00:00
extras | 3.4 kB 00:00
mysql-connectors-community | 2.5 kB 00:00
mysql-tools-community | 2.5 kB 00:00
mysql56-community | 2.5 kB 00:00
plesk-migrator | 2.9 kB 00:00
plesk-migrator-tp | 2.9 kB 00:00
remi-safe | 2.9 kB 00:00
updates | 3.4 kB 00:00
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.5.60-1.el6.remi will be obsoleted
--> Processing Dependency: real-mysql(x86-64) = 5.5.60-1.el6.remi for package: mysql-server-5.5.60-1.el6.remi.x86_64
---> Package mysql-community-client.x86_64 0:5.6.40-2.el6 will be obsoleting
--> Processing Dependency: mysql-community-libs(x86-64) >= 5.6.10 for package: mysql-community-client-5.6.40-2.el6.x86_64
--> Running transaction check
---> Package mysql-community-libs.x86_64 0:5.6.40-2.el6 will be obsoleting
--> Processing Dependency: mysql-community-common(x86-64) >= 5.6.10 for package: mysql-community-libs-5.6.40-2.el6.x86_64
---> Package mysql-community-server.x86_64 0:5.6.40-2.el6 will be obsoleting
--> Processing Dependency: libnuma.so.1(libnuma_1.2)(64bit) for package: mysql-community-server-5.6.40-2.el6.x86_64
--> Processing Dependency: libnuma.so.1(libnuma_1.1)(64bit) for package: mysql-community-server-5.6.40-2.el6.x86_64
--> Processing Dependency: libnuma.so.1()(64bit) for package: mysql-community-server-5.6.40-2.el6.x86_64
---> Package mysql-libs.x86_64 0:5.5.60-1.el6.remi will be obsoleted
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4.45-14.el6.remi.x86_64
---> Package mysql-server.x86_64 0:5.5.60-1.el6.remi will be obsoleted
--> Running transaction check
---> Package mysql-community-common.x86_64 0:5.6.40-2.el6 will be installed
---> Package mysql-libs.x86_64 0:5.5.60-1.el6.remi will be obsoleted
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4.45-14.el6.remi.x86_64
---> Package numactl.x86_64 0:2.0.9-2.el6 will be installed
--> Finished Dependency Resolution
Error: Package: php-mysql-5.4.45-14.el6.remi.x86_64 (@Remi)
Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit)
Removing: mysql-libs-5.5.60-1.el6.remi.x86_64 (@Remi)
libmysqlclient.so.18(libmysqlclient_16)(64bit)
Obsoleted By: mysql-community-libs-5.6.40-2.el6.x86_64 (mysql56-community)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
 
This falls firmly into the "more hassle than it is worth category" If possible spin up a new server with new software and migrate your site into the new environment. other wise as you can see you have multiple repos on there which seem to be confusing the picture and have landed you in dependency hell. You could try disabling some repos if they are not in use. Or you could try to use Docker to host the new mysql version.. not tried this but it should work
 
Back
Top