[SERVER-16862] Redhat YUM repository metadata checksum Created: 15/Jan/15 Updated: 02/Feb/15 Resolved: 23/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 2.6.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Clive Miller | Assignee: | Ernie Hershey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Follow installation instructions at http://docs.mongodb.org/manual/tutorial/install-mongodb-on-red-hat-centos-or-fedora-linux/ |
| Participants: |
| Description |
|
I'm trying to install mongodb on a completely newly-built machine. Worked yesterday, but today does not.
One of the configured repositories failed (MongoDB Repository), 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 3. Disable the repository, so yum won't use it by default. Yum will then yum-config-manager --disable mongodb 4. Configure the failing repository to be skipped, if it is unavailable. yum-config-manager --save --setopt=mongodb.skip_if_unavailable=true failure: repodata/primary.xml.gz from mongodb: [Errno 256] No more mirrors to try. |
| Comments |
| Comment by Clive Miller [ 02/Feb/15 ] | |||||||||||||
|
That's a good idea. Thank you. | |||||||||||||
| Comment by Ernie Hershey [ 30/Jan/15 ] | |||||||||||||
|
clivemiller - I think this is fixed in later versions of the RPM "createrepo" command than the one we're using now by creating unique metadata filenames so they won't occupy the same slots in http caches. We have plans to generate package repositories on more up to date servers in the near future which should eliminate the problem. | |||||||||||||
| Comment by Clive Miller [ 15/Jan/15 ] | |||||||||||||
|
Ah - problem solved. I'm working through Squid proxy. I cleared out the cache and now it works. Sorry! Is there something you can do to your server so that Squid doesn't continue to use an out-of-date cached page? | |||||||||||||
| Comment by Clive Miller [ 15/Jan/15 ] | |||||||||||||
|
redhat-release:
Yum version
Although this is CentOS, it did work successfully yesterday. | |||||||||||||
| Comment by Ernie Hershey [ 15/Jan/15 ] | |||||||||||||
|
clivemiller - can you try again? This may have been a transient error while we were updating the repository for 2.6.7. I just verified that it's working right now for me in rhel 7. If you're still having trouble can you let me know your exact OS and OS version and yum version? e.g.
Thanks, |