Yum Maria update fails

[Steve Kemp]

I have just notied on one of our servers that we are getting an error when running Yum Update:

http://yum.mariadb.org/10.6/centos7-amd64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to yum.mariadb.org:80; Operation now in progress"

if i temporarily disable the repo yum completes but anyone know why this would be occuring or how to resolve?

 

[andrew.n]

hm could be a temporary issue with their repo. Could you do "yum clean all" and run "yum update" again?

 

[cPRex]

I'm not seeing an issue with the repo when I check things right now. If you still see an issue with this after trying the command that @andrew.n mentioned, please let us know!

 

[bogmar88]

Hello,

I have the same problem on a new server, after the cPanel was installed.
I can`t upgrade to MariadDB 10.3

[[email protected] ~]# yum update
Loaded plugins: fastestmirror, langpacks, universal-hooks
Determining fastest mirrors
* EA4: 178.x.x.x
* cpanel-addons-production-feed: 178.x.x.x
* cpanel-plugins: 178.x.x.x
* base: mirror.checkdomain.de
* extras: ftp.plusline.net
* updates: linux.darkpenguin.net
EA4 | 2.9 kB 00:00:00
cpanel-addons-production-feed | 2.9 kB 00:00:00
cpanel-plugins | 2.9 kB 00:00:00
https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

yum-errors - CentOS Wiki

If above article doesn't help to resolve this issue please use My View - CentOS Bug Tracker.



One of the configured repositories failed (MariaDB102),
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=MariaDB102 ...

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 MariaDB102
or
subscription-manager repos --disable=MariaDB102

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=MariaDB102.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB102: [Errno 256] No more mirrors to try.
https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
[[email protected] ~]# [[email protected] ~]# yum update

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=MariaDB102 ...

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 MariaDB102
or
subscription-manager repos --disable=MariaDB102

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=MariaDB102.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB102: [Errno 256] No more mirrors to try.
https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found-bash: [[email protected]: command not found

 

[cPRex]

@bogmar88 - you'll want to see my post here for more details:

SOLVED - One of the configured repositories failed (MariaDB106)

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...

forums.cpanel.net

The short story, is that we have to reprogram our MySQL update tool to work with the recent MariaDB repository changes.