Skip to main content

One of the configured repositories failed (MariaDB106)

greektranslator
I get the error below when trying yum update. 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

Comments

39 comments

Date Votes
  • cPRex Jurassic Moderator
    If the manual tools aren't working, it would be best to submit a ticket. We may be able to create a workaround that is specific to your machine until the case is resolved.
    0
  • Boris Horvat
    great... WORKING... Thank You
    0
  • cPRex Jurassic Moderator
    I'm glad that's working well for you now!
    0
  • billy.gladky
    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
    Thank you after no sleep 2 nights over this.
    0
  • Lee Roberts
    @Boris Horvat - if you need to perform the upgrade immediately, you can do this: then perform the update, then remove that hosts file entry. We plan to have issue number 3 resolved on our side this week.

    Cheers @cPRex this worked for me today as well :)
    0
  • jasolution1
    We plan to have issue number 3 resolved on our side this week.

    Has this been pushed out in an official release yet?
    0
  • cPRex Jurassic Moderator
    The update was released with 106.0.5 and has also been backported to LTS 102.0.21.
    0
  • Jefferson Daciano
    OLA BOA NOITE A TODOS ESTOU COM O MESMO PROBLEMA e n"o consigo sair deste cen"rio algu"m tem outro m"todo mais simples por favor ?
    0
  • cPRex Jurassic Moderator
    @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?
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post