Details
-
Bug
-
Resolution: Done
-
Minor - P4
-
None
-
None
-
AWS Ec2 Instance.
amzn-ami-pv-2015.03.0.x86_64-ebs (ami-bf0897c8)
*Location*: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-red-hat/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36
*Referrer*: https://www.google.co.uk/
*Screen Resolution*: 1280 x 800
*repo*: docs
*source*: tutorial/install-mongodb-on-red-hat
AWS Ec2 Instance. amzn-ami-pv-2015.03.0.x86_64-ebs (ami-bf0897c8) *Location*: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-red-hat/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36 *Referrer*: https://www.google.co.uk/ *Screen Resolution*: 1280 x 800 *repo*: docs *source*: tutorial/install-mongodb-on-red-hat
Description
I've followed your instructions and i've gone to run the command `sudo yum install -y mongodb-org` and i'm getting the following error message:
https://repo.mongodb.org/yum/redhat/latest/mongodb-org/3.0/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
|
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
|
|
|
failure: repodata/repomd.xml from mongodb-org-3.0: [Errno 256] No more mirrors to try.
|