One of the configured repositories failed (MariaDB106)
I get the error below when trying yum update.
These are my repos:
System update process has started.
"/usr/bin/yum" reported error code "1" when it ended: w/ /usr/bin/yum upgrade -y
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* 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
http://yum.mariadb.org/10.6/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
One of the configured repositories failed (MariaDB106),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=MariaDB106 ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable MariaDB106
or
subscription-manager repos --disable=MariaDB106
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=MariaDB106.skip_if_unavailable=true
failure: repodata/repomd.xml from MariaDB106: [Errno 256] No more mirrors to try.
http://yum.mariadb.org/10.6/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Often errors like this can be resolved by running `yum makecache`
System update process has finished.
These are my repos:
yum repolist enabled
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* 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
EA4 | 2.9 kB 00:00
EA4-experimental | 2.9 kB 00:00
cpanel-addons-production-feed | 2.9 kB 00:00
cpanel-plugins | 2.9 kB 00:00
http://yum.mariadb.org/10.6/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article
https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
EA4/7/x86_64/primary_db | 2.7 MB 00:00
EA4-experimental/7/x86_64/primary_db | 116 kB 00:00
cpanel-addons-production-feed/x86_64/primary_db | 19 kB 00:00
cpanel-plugins/x86_64/primary_db | 41 kB 00:00
http://yum.mariadb.org/10.6/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP E rror 404 - Not Found
Trying other mirror.
base/7/x86_64 | 3.6 kB 00:00
base/7/x86_64/group_gz | 153 kB 00:00
base/7/x86_64/primary_db | 6.1 MB 00:00
extras/7/x86_64 | 2.9 kB 00:00
extras/7/x86_64/primary_db | 247 kB 00:00
imunify360 | 3.0 kB 00:00
imunify360/primary_db | 1.1 MB 00:01
imunify360-rollout-1/7 | 3.0 kB 00:00
imunify360-rollout-1/7/primary_db | 1.4 kB 00:00
imunify360-rollout-2/7 | 3.0 kB 00:00
imunify360-rollout-2/7/primary_db | 1.4 kB 00:00
imunify360-rollout-3/7 | 3.0 kB 00:00
imunify360-rollout-3/7/primary_db | 1.4 kB 00:00
imunify360-rollout-4/7 | 3.0 kB 00:00
imunify360-rollout-4/7/primary_db | 1.4 kB 00:00
metrics/7/x86_64 | 2.9 kB 00:00
metrics/7/x86_64/primary_db | 9.6 kB 00:00
rtm/7/x86_64 | 2.9 kB 00:00
rtm/7/x86_64/primary_db | 9.0 kB 00:00
updates/7/x86_64 | 2.9 kB 00:00
updates/7/x86_64/primary_db | 16 MB 00:00
wp-toolkit-cpanel | 2.9 kB 00:00
wp-toolkit-cpanel/primary_db | 3.3 kB 00:00
wp-toolkit-thirdparties | 2.9 kB 00:00
wp-toolkit-thirdparties/primary_db | 14 kB 00:00
repo id repo name status
EA4/7/x86_64 EA4 ( EasyApache 4 ) 9,865
EA4-experimental/7/x86_64 EA4 Experimental ( EasyApache 4 ) 367
cpanel-addons-production-feed/x86_64 cPanel Addons Production Feed 68
cpanel-plugins/x86_64 cPanel Plugins project 93
MariaDB106 MariaDB106 0
base/7/x86_64 CentOS-7 - Base 10,072
extras/7/x86_64 CentOS-7 - Extras 512
imunify360 EL-7 - Imunify360 2,774
imunify360-rollout-1/7 Imunify360 - Gradual Rollout Slot 1 0
imunify360-rollout-2/7 Imunify360 - Gradual Rollout Slot 2 0
imunify360-rollout-3/7 Imunify360 - Gradual Rollout Slot 3 0
imunify360-rollout-4/7 Imunify360 - Gradual Rollout Slot 4 0
metrics/7/x86_64 OVH METRICS RHEL/ CentOS 7 - x86_64 35
rtm/7/x86_64 OVH RTM RHEL/ CentOS 7 - x86_64 27
updates/7/x86_64 CentOS-7 - Updates 4,101
wp-toolkit-cpanel WordPress Toolkit for cPanel 1
wp-toolkit-thirdparties WordPress Toolkit third parties 16
repolist: 27,931
-
Seeing the same on my servers with MariaDB 10.3 since yesterday. 0 -
Today I noticed that repos for Centos 7 versions higher than Mariadb 10.2 were deleted but I couldn't find an official explanation. Does anyone know what causes the problem? 0 -
Seeing the same on my servers with MariaDB 10.3 since yesterday.
I'm seeing this (MariaDB103) too...0 -
Same issue 0 -
Hey there! We aren't sure either, but we've reached out to MariaDB to see what's going on. I don't have anything to report yet except that this is an upstream issue and not something cPanel can resolve, but once I hear back I'll be sure to post more details. 0 -
Same issue (MariaDB106) 0 -
Update - it looks like MariaDB has adjusted their mirrors and things are working well again. If you're still seeing issues, try the typical commands of: yum clean all yum makecache
before performing an update and I would expect things to work well at this point.0 -
Hi all, I'm getting this error: Error: Failed to download metadata for repo 'MariaDB105': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Edit: Seems to be all fixed now. :) 0 -
Back to not working, for me [font="courier new">[plain]# curl http://mirror.mariadb.org/yum/10.3/centos7-amd64/repodata/repomd.xml Not Found[/plain] 0 -
And... it's back! Problem still appears to be fluid. Probably less "SOLVED" and more "VENDOR IS AWARE... maybe" 0 -
MariaDB told us it was solved at 12:30 yesterday, so it could be things were still settling on their end. Are things looking better for everyone today? 0 -
At the repo there are no 10.2 version. Here the repo link Index of /yum/ 0 -
@Eliavz - that is normal, as that version has reached End of Life - MariaDB 0 -
Unfortunately the problem persists. All installations in the data center have stopped since yesterday! When we select Mysql 5.7 > MariaDB 10.6, it automatically installs 10.2., checkyum version 22.3 (excludes: bind-chroot) Ensuring that the package "MariaDB-client" with version matching "10.2" is available. Isn't there an easy solution? MariaDB told us it was solved at 12:30 yesterday, so it could be things were still settling on their end. Are things looking better for everyone today?
0 -
same problem here... Unfortunately the problem persists. All installations in the data center have stopped since yesterday! When we select Mysql 5.7 > MariaDB 10.6, it automatically installs 10.2., checkyum version 22.3 (excludes: bind-chroot) Ensuring that the package "MariaDB-client" with version matching "10.2" is available. Isn't there an easy solution?
this is not solution...For people seeing issues with MariaDB updates, the following document should be helpful:
0 -
This problem is not SOLVED 0 -
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. 0 -
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. 0 -
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. 0 -
Is the fix ready for update? 0 -
Has there been any progress made on this issue? Thank you! 0 -
Issue number 3 from my list still hasn't been resolved just yet. Since this is affecting many users, I'm hoping the fix will go public sooner than later, as it's currently moving through our QA team. 0 -
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 0 -
Issue number 3 still hasn't been resolved? Can you write me how to properly replace MYSQL 5.7 with MariaDB 10.5 manually because I can't wait for you to fix this bug. Tnx 0 -
@Boris Horvat - if you need to perform the upgrade immediately, you can do this: echo '142.4.217.28 yum.mariadb.org' >> /etc/hosts
then perform the update, then remove that hosts file entry. We plan to have issue number 3 resolved on our side this week.0 -
@cPRex This does not work... upgrade failed again... The system was not able to ensure the availability of the "MariaDB-client" package: The package "MariaDB-client" with version "10.5" is not available via yum: Loaded plugins: fastestmirror, universal-hooks 0 -
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 0
Please sign in to leave a comment.
Comments
39 comments