Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20095

Redhat repository broken - Metadata file does not match checksum

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Packaging
    • None
    • Fully Compatible
    • ALL
    • Hide

      Fresh install of CentOS 7.

      $ cat /etc/yum.repos.d/mongodb-org-3.0.repo
       
      [mongodb-org-3.0]
      name=MongoDB Repository
      baseurl=https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/
      gpgcheck=0
       
      $ yum search mongo
      

      Show
      Fresh install of CentOS 7. $ cat /etc/yum.repos.d/mongodb-org-3.0.repo   [mongodb-org-3.0] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/ gpgcheck=0   $ yum search mongo

    Description

      Similar problem to SERVER-20087.

      mongodb-org-3.0/primary                                                                                      | 8.9 kB  00:00:00     
      https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
      Trying other mirror.
       
       
       One of the configured repositories failed (MongoDB Repository),
       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. Disable the repository, 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 mongodb-org-3.0
       
           4. 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=mongodb-org-3.0.skip_if_unavailable=true
      

      Attachments

        Activity

          People

            ernie.hershey@mongodb.com Ernie Hershey
            alee@intellisurvey.com Andy Lee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: