Skip to main content

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.

Answered
greektranslator
  • Edited

I get the above error when I try yum update. Using CentOS v7.9.2009 STANDARD

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Also, I tried to change the php version of a domain and when I use Domain Settings, PHP-FPM appears unavailable and prompts to update php, but when I try the link for Php manager it keeps loading ad infinitum.

Comments

8 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  You probably need to adjust your server to use the vault mirrors as outlined here, as CentOS 7 is no longer supported:

    https://support.cpanel.net/hc/en-us/articles/24571139547415-Could-not-retrieve-mirrorlist-http-mirrorlist-centos-org-on-CentOS-7

    Can you try that and see if that helps?

    1
  • greektranslator

    Thanks, fixed!

    0
  • cPRex Jurassic Moderator

    I'm glad that took care of things!

    0
  • greektranslator

    What I get now is:

     

    [root@host ~]# yum update
    Loaded plugins: fastestmirror, universal-hooks
    Loading mirror speeds from cached hostfile
     * EA4: 185.15.22.168
     * EA4-experimental-c7: 185.15.22.168
     * cpanel-addons-production-feed: 185.15.22.168
     * cpanel-plugins: 185.15.22.168
    https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
    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 (CentOS 7 Extended Lifecycle Support by TuxCare),
     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=centos7-els ...

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

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

    failure: repodata/repomd.xml from centos7-els: [Errno 256] No more mirrors to try.
    https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden

    0
  • greektranslator

    Looks like I had to purchase a license from Tuxcare... This information was nowhere to be found on the Extended Support documentation.

    0
  • greektranslator
    • Edited

    How can I know if my cPanel license included ELS coverage anyway? I got this from Tuxcare

    Yes, typically cPanel licenses do include ELS coverage, but in some instances this might not be the case. The best option would be checking the available perks for your server's IP here. If it includes access to the ELS repositories, we would suggest reaching out to cPanel's team so they can provide you with the license, and register the server again with the "--force" option and the new key.

    1
  • cPRex Jurassic Moderator

    greektranslator - I spoke with our Customer Service team and they informed me that the only requirement is that your server is licensed and running CentOS 7, so you'd likely need to open a ticket to find out why you didn't get that automatically applied to your machine.

    0
  • Darryl

    I had to ticket about this also and the workaround was simple, an issue with ipv6, including below:

    https://support.cpanel.net/hc/en-us/articles/26988081123607-ELS-repo-returns-403-if-connections-use-IPv6

     

    Add 'ip_resolve=4' to the ELS repo file: 

     

    /etc/yum.repos.d/centos7-els.repo

     

    Afterwards yum works fine.

     

     

    2

Please sign in to leave a comment.

Didn't find what you were looking for?

New post