Upgrade MySQL 5.6 to MariaDB 10.3 fails due to repo problem
As MySQL ran out of date I decided to upgrade from MySQL 5.6 to MariaDB 10.3.
Unfortunately the migration wizard quits quite early while [QUOTE]Ensuring that the package "MariaDB-client" with version matching "10.0" is available.
with the following error [QUOTE]The system was not able to ensure the availability of the "MariaDB-client" package: (XID ebedq2) "/usr/bin/yum" reported error code "1" when it ended: Error: No matching Packages to list Obtained version information from system.
I therefore checked where to find the MariaDB-Client package
As you can see there is no package MariaDB_client available. Double-checked that with the MariaDB repo only et voil"
The netcup mirror repo has a "priority=1" option enabled. Completely disabling the netcup mirror seems to be no good idea. Inserting a "priority=1" into the MariaDB100 repo seems to be useless as the upgrade wizard re-writes the repo each time. As the upgrade process iterates through the MariaDB versions what is the safest way to ensure that in every single migration step the actual needed MariaDB repo is used?
with the following error [QUOTE]The system was not able to ensure the availability of the "MariaDB-client" package: (XID ebedq2) "/usr/bin/yum" reported error code "1" when it ended: Error: No matching Packages to list Obtained version information from system.
I therefore checked where to find the MariaDB-Client package
yum list all maria*
Loaded plugins: fastestmirror, priorities, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 185.53.12.144
* cpanel-addons-production-feed: 185.53.12.144
* cpanel-plugins: 185.53.12.144
* base: centosmirror.netcup.net
* extras: centosmirror.netcup.net
* updates: centosmirror.netcup.net
11739 packages excluded due to repository priority protections
Available Packages
MariaDB-cassandra-engine.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-common.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-compat.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-connect-engine.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-oqgraph-engine.x86_64 10.0.38-1.el7.centos MariaDB100
mariadb.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-bench.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-devel.i686 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-devel.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-embedded.i686 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-embedded.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-embedded-devel.i686 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-embedded-devel.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-libs.i686 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-libs.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-server.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
mariadb-test.x86_64 1:5.5.60-1.el7_5 centosmirror.netcup.net_centos_7_os_x86_64_
As you can see there is no package MariaDB_client available. Double-checked that with the MariaDB repo only et voil"
yum --disablerepo="*" --enablerepo="MariaDB100" list available
Loaded plugins: fastestmirror, priorities, universal-hooks
Loading mirror speeds from cached hostfile
Available Packages
MariaDB-Galera-server.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-Galera-test.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-cassandra-engine.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-client.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-common.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-compat.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-connect-engine.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-devel.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-oqgraph-engine.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-server.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-shared.x86_64 10.0.38-1.el7.centos MariaDB100
MariaDB-test.x86_64 10.0.38-1.el7.centos MariaDB100
galera.x86_64 25.3.25-1.rhel7.el7.centos MariaDB100
jemalloc.x86_64 3.6.0-1.el7 MariaDB100
jemalloc-devel.x86_64 3.6.0-1.el7 MariaDB100
libzstd.x86_64 1.3.4-1.el7 MariaDB100The netcup mirror repo has a "priority=1" option enabled. Completely disabling the netcup mirror seems to be no good idea. Inserting a "priority=1" into the MariaDB100 repo seems to be useless as the upgrade wizard re-writes the repo each time. As the upgrade process iterates through the MariaDB versions what is the safest way to ensure that in every single migration step the actual needed MariaDB repo is used?
-
cpanel doesn't yet support MariaDB 10.3 and trying to install it outside of cpanel is not advisable. 0 -
Running the release tier (v78.0.13), MariaDB 10.3 is the 'recommended' version. 0 -
Oh ha I must have been checking a 76 server Sorry about that! Best bet would probably be a ticket then. 0 -
Hello @SamSpade, I'm glad to see you were able to solve the issue. Can you send me a private message with the name of your hosting provider? I'd like to reach out to them to provide details about this issue in an effort to reduce the number of systems affected by the same issue. Thanks! 0
Please sign in to leave a comment.
Comments
6 comments