CentOS 6 Update Issues

Home » CentOS » CentOS 6 Update Issues
CentOS 16 Comments

Hello all,

I manage a few servers overseas that are running CentOS 6.

When performing a yum update, it fails because it’s trying to download from:

mirror.CentOS.org/CentOS/*6.6*/extras/x86_64/repodata/repomd.xml

Which fails due to the fact that the entire 6.6 directory is empty on all of the mirrors I have checked. From what I can tell it should be using:

mirror.CentOS.org/CentOS/*6*/extras/x86_64/repodata/repomd.xml

Does anyone have any idea why this would be happening? Obviously changing the CentOS-Base file to use ‘baseurl’ rather than ‘mirrorlist’ is a workaround, but I would prefer a more permanent solution, and would like to know why this is happening.

Thanks in advance.

16 thoughts on - CentOS 6 Update Issues

  • Hi, in most cases you would expect mirrorlist to be defined rather than baseurl unless you want to be pointing to a specific repository. I would suggest that you do a fresh install somewhere update it and then compare the files in /etc/yum.repos.d/ with your existing systems.

    As examples of base and updates from one of my own systems I have

    [base]
    name

  • I had something similar happen recently when upgrading a box from 6.6 to 6.7

    I ‘fixed’ it by running ‘yum clean all’ first

    I did think it odd at the time – but didn’t get round to trying to find out why …

    James Pearson

  • John Cenile wrote:

    Also check you don’t have the file /etc/yum/vars/releasever – the contents of this will override the value of $releasever in the repo files

    James Pearson

  • In your initial post you mentioned problems with extras. Here you are changing the stanza of base. What is your stanza for “extras”?

  • Thanks for the suggestions, unfortunately that file doesn’t exist.

    I’m very confused as to why it’s trying to download from /6.6/.

    The output of rpm -qi CentOS-release-6-4.el6.CentOS.10.x86_64 is:

    Name : CentOS-release Relocations: (not relocatable)
    Version : 6 Vendor: CentOS
    Release : 4.el6.CentOS.10 Build Date: Mon 25 Feb 2013
    07:57:43 PM EST
    Install Date: Fri 05 Jul 2013 09:32:33 AM EST Build Host:
    c6b8.bsys.dev.CentOS.org Group : System Environment/Base Source RPM:
    CentOS-release-6-4.el6.CentOS.10.src.rpm Size : 32670 License: GPLv2
    Signature : RSA/SHA1, Sat 02 Mar 2013 01:01:26 AM EST, Key ID
    0946fca2c105b9de Packager : CentOS BuildSystem <http://bugs.CentOS.org>
    Summary : CentOS release file Description :
    CentOS release files

  • What does this command give you from that machine:

    curl “http://mirrorlist.CentOS.org/?release=6&arch=x86_64&repo=extras”

    Are you using ipv4 or ipv6?

  • I’m actually not able to connect to that host:

    # curl “http://mirrorlist.CentOS.org/?release=6&arch=x86_64&repo=extras”
    curl: (7) couldn’t connect to host

    Which lead me to discover that our entire network is picking up ”
    mirrorlist.CentOS.org” as 204.15.73.243, which I’m not able to ping from any host in a few different countries I tried.

    However, if I ping mirrorlist.CentOS.org from Europe, it resolves to 84.22.180.89, or from USA it resolves to 88.150.173.218, or from Asia it resolves to 108.61.16.227.

    Could there be an issue with this specific mirrorlist server
    (204.15.73.243)?

  • Those 3 addresses are good, the 204.15.73.243 is incorrect.

    Yes, that address is not listed in our DNS zone file for mirrorlist. In fact, that address is not in our zone file for anything .. so I have no idea where you are getting it looked up from.

  • I don’t think so on our end, but that was at one time a good address.

    Maybe the site in question has a static address added in a hosts file, etc.

  • Hello Johnny,

    That appears to be it, our network DNS resolvers were caching an old record from the looks of it.

    I’ve cleared the cache, and everything is now working perfectly.

    Thank you (all) for the help, I wasn’t even aware that the 204.15.73.243
    address was no longer valid.