How to fix this MariaDB yum upgrade error?

[sychn]

Hi m8s,

Does anyone know how to fix this MariaDB yum upgrade error?

Thanks in advance!

 

[root@sychn ~]# yum clean all
Loaded plugins: fastestmirror
Cleaning repos: base city-fan.org epel extras mariadb remi-php80 remi-safe
              : updates
Cleaning up list of fastest mirrors
Other repos take up 3.0 M of disk space (use --verbose for details)
[root@sychn ~]# rm -rf /var/cache/yum/*
[root@sychn ~]# yum upgrade
Loaded plugins: fastestmirror
Determining fastest mirrors
 * city-fan.org: www.city-fan.org
 * remi-php80: ftp.riken.jp
 * remi-safe: ftp.riken.jp
base                                                     | 3.6 kB     00:00
city-fan.org                                             | 3.0 kB     00:00
epel                                                     | 4.7 kB     00:00
extras                                                   | 2.9 kB     00:00
http://yum.mariadb.org/10.2/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 (MariaDB),
 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=mariadb ...

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

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

failure: repodata/repomd.xml from mariadb: [Errno 256] No more mirrors to try.
http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

 

[Randy Calvert]

The MariaDB repo you're trying to call is not responding.  In looking at the URL (http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml), it shows up as a 404 error.  So yes...  it indeed does look to be a bad repo.  

The output above actually gives you your available options...  you can permanently disable that repo by running:

yum-config-manager --disable mariadb

[sychn]

6 hours ago, Randy Calvert said:

The MariaDB repo you're trying to call is not responding.  In looking at the URL (http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml), it shows up as a 404 error.  So yes...  it indeed does look to be a bad repo.  

The output above actually gives you your available options...  you can permanently disable that repo by running:

yum-config-manager --disable mariadb

Thanks. But if I permanently disable that repo, can yum upgrade MariaDB in the future? or should I add a new repo?

[Randy Calvert]

In that case, you would want option 2 in that list. Edit the baseurl to point to a different (hopefully working) repository. 🙂 

Also MariaDB may be already in one of those other channels you subscribe to. You might want to confirm that before spending time on adding different repos.
 

If it is, just remove the bad repo and call it a day. If not, find an alternative and add it and disable the bad one. 

Edited November 29, 2022 by Randy Calvert

[sychn]

18 minutes ago, Randy Calvert said:

In that case, you would want option 2 in that list. Edit the baseurl to point to a different (hopefully working) repository. 🙂 

Also MariaDB may be already in one of those other channels you subscribe to. You might want to confirm that before spending time on adding different repos.
 

If it is, just remove the bad repo and call it a day. If not, find an alternative and add it and disable the bad one. 

Thanks Randy, it helps 👍