SOLVED One of the configured repositories failed (MariaDB106)

Boris Horvat

Active Member
Jul 29, 2014
26
1
51
Split, Croatia, Croatia
cPanel Access Level
Root Administrator
Try to upgrade from Mysql 5.7 to MariaDB 10.5 and get this error:

Starting process with log file at /var/cpanel/logs/mysql_upgrade.20220817-053802/unattended_upgrade.log
Beginning “MariaDB 10.3” upgrade...
Obtained version information from system.
Ensuring the “MariaDB102” repository is available and working.
distro does not use package modules; ignoring request to disable mysql
distro does not use package modules; ignoring request to disable mariadb
checkyum version 22.3 (excludes: bind-chroot)
Ensuring that the package “MariaDB-client” with version matching “10.2” is available.
Restarting mysql service.
Waiting for “mysql” to restart ……waiting for “mysql” to initialize ………finished.

Service Status
mysqld (/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid) is running as mysql with PID 32725 (systemd+/proc check method).

Startup Log
Aug 17 05:38:09 server.dalmacijadanas.hr systemd[1]: Starting MySQL Server...
Aug 17 05:38:10 server.dalmacijadanas.hr systemd[1]: Started MySQL Server.

Log Messages
2022-08-17T05:38:10.555465Z 0 [Note] /usr/sbin/mysqld: ready for connections.
2022-08-17T05:38:09.677673Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
2022-08-17T05:38:08.564439Z 0 [Warning] /usr/sbin/mysqld: Forcing close of thread 12 user: 'root'

mysql restarted successfully.
The system was not able to ensure the availability of the “MariaDB-client” package: The package “MariaDB-client” with version “10.2” is not available via yum: Loaded plugins: fastestmirror, universal-hooks
Determining fastest mirrors
* EA4: 185.15.22.168
* EA4-experimental: 185.15.22.168
* cpanel-addons-production-feed: 185.15.22.168
* cpanel-plugins: 185.15.22.168
* epel: mirror.23m.com
Available Packages
MariaDB-client.x86_64 10.3.36-1.el7.centos MariaDB102
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MariaDB enables "strict mode" by default as of version 10.2. Strict mode controls how MariaDB and MySQL handle invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MariaDB are compatible before upgrading. More information about strict mode is available here. Critical: In MariaDB® 10.3, the mysqldump client includes logic for the mysql.transaction_registry table. You cannot use the mysqldump client from an earlier MariaDB release on MariaDB 10.3 and later. For more information about how to upgrade to MariaDB 10.3, read the MariaDB upgrade documentation. Normal: The selected MariaDB version (10.3) is more than one generation newer than the currently installed version. The upgrade process will iterate over each intervening version to ensure tables are upgraded appropriately.
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
12,494
1,967
363
cPanel Access Level
Root Administrator
I have some updates about these issues.

The first thing, is that we need to clarify the issues being addressed here. The problem on Monday was that MariaDB broke their mirrors, so *any* check of a MariaDB update would fail, and Yum issues would be reported to the server admin. This issue has been resolved.

The secondary issue that many people are reporting, is the upgrade from some older version to MariaDB 10.0, 10.2, etc. That is a separate issue, also caused by how MariaDB changed their mirror structure, and we have a fix that is going to be released today on our end to address this.

The fix will be to change the Yum configuration on the server to point to the archive.mariadb.org repository, as even though it has the "archive" name it has every version available, including older versions that have been removed from the "official" mirror/repository. This will resolve the issues people are seeing with MySQL upgrades, the EasyApache interface, and will also keep any future problems from happening when version 10.3 eventually reaches end-of-life and is no longer accessible through the "official" repository.

That fix is expected to go out later this afternoon, and will run tonight as part of the automatic updates on the machine.
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
12,494
1,967
363
cPanel Access Level
Root Administrator
Update: it seems there are actually three separate issues. I'll explain each of those below and when they will get fixed:

1 - Sunday night/Monday's issue with broken repositories: MariaDB has solved this on their side.
2 - MariaDB 10.2 repository missing: MariaDB removed this version from their standard repositories. We're updating the path that Yum looks for to use their archive repository, which contains everything. This will also solve update issues moving forward. This is the fix we are pushing out during tonight's update.
3 - Updating from MySQL to MariaDB, like what @Boris Horvat reported. This is a separate, but similar, issue to number 2, where version 10.2 has been removed from the MariaDB repositories that we have programmed into our update tool. This is not yet fixed as we have to change our tool, but the developers are working on this now in case BOO-2217.

I'll be sure to post more updates as I get them.
 

rbairwell

Well-Known Member
May 28, 2022
95
38
18
Mansfield, Nottingham, UK
cPanel Access Level
Root Administrator
Since I've hit this problem on a new server migrating from MySQL to MariaDB (and my much earlier post about how to fix the general issue seems to have just expired rather than be approved), here's what I did to fix it.

Platform: Centos v7.9 on x64 - migrating from MySQL 5.7 to MariaDB 10.6

If you do not have /etc/yum.repos.d/MariaDB102.repo , start an upgrade to MariaDB and let it die.

1. Copy /etc/yum.repos.d/MariaDB102.repo to /etc/yum.repos.d/MariaDB102-patch.repo
2. Modify /etc/yum.repos.d/MariaDB102-patch.repo to change the baseurl to https://archive.mariadb.org/mariadb-10.2/yum/centos7-amd64
3. Copy that file now as /etc/yum.repos.d/MariaDB103-patch.repo
4. Modify MariaDB103-patch.repo so "102" is changed to "103" throughout and the base URL has 10.3
5. Repeat steps 3 and 4 to go from "103/10.3" to "104/10.4" etc all the way up to 106/10.6
6. Do yum clean all;yum makecache
7. Go to the Database upgrade page (select "Ignore current upgrade" if necessary)
8. And upgrade!

Bit long winded and fiddly, but it worked for me(tm)
 

mark135uk

Member
May 7, 2014
11
1
53
cPanel Access Level
Website Owner
does anyone know what file i need to edit to specify a new install i want mariadb over mysql? i know i need to reinstall whm after but i cannot remember the file i need to edit
 

billy.gladky

Registered
Jan 23, 2020
2
0
1
US
cPanel Access Level
Root Administrator
Since I've hit this problem on a new server migrating from MySQL to MariaDB (and my much earlier post about how to fix the general issue seems to have just expired rather than be approved), here's what I did to fix it.

Platform: Centos v7.9 on x64 - migrating from MySQL 5.7 to MariaDB 10.6

If you do not have /etc/yum.repos.d/MariaDB102.repo , start an upgrade to MariaDB and let it die.

1. Copy /etc/yum.repos.d/MariaDB102.repo to /etc/yum.repos.d/MariaDB102-patch.repo
2. Modify /etc/yum.repos.d/MariaDB102-patch.repo to change the baseurl to https://archive.mariadb.org/mariadb-10.2/yum/centos7-amd64
3. Copy that file now as /etc/yum.repos.d/MariaDB103-patch.repo
4. Modify MariaDB103-patch.repo so "102" is changed to "103" throughout and the base URL has 10.3
5. Repeat steps 3 and 4 to go from "103/10.3" to "104/10.4" etc all the way up to 106/10.6
6. Do yum clean all;yum makecache
7. Go to the Database upgrade page (select "Ignore current upgrade" if necessary)
8. And upgrade!

Bit long winded and fiddly, but it worked for me(tm)

Thank you after no sleep 2 nights over this.
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
12,494
1,967
363
cPanel Access Level
Root Administrator
@Jefferson Daciano - você pode me informar o problema exato que você está vendo? Qual é a mensagem de erro específica?

*************************************************************************************************************

can you let me know the exact problem you are seeing? What is the specific error message?