-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:
-
Environment:Amazon Linux AMI release 2015.09
*Location*: https://docs.mongodb.org/master/tutorial/install-mongodb-on-amazon/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0
*Referrer*: https://docs.mongodb.org/master/tutorial/install-mongodb-on-linux/
*Screen Resolution*: 1920 x 1200
*repo*: docs
*source*: tutorial/install-mongodb-on-amazon
Amazon Linux AMI release 2015.09 *Location*: https://docs.mongodb.org/master/tutorial/install-mongodb-on-amazon/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 *Referrer*: https://docs.mongodb.org/master/tutorial/install-mongodb-on-linux/ *Screen Resolution*: 1920 x 1200 *repo*: docs *source*: tutorial/install-mongodb-on-amazon
Hi, i am trying to install mongoDB 3.2 and this is the error message i am getting after following the instruction listed here;
https://repo.mongodb.org/yum/amazon/2013.03/mongodb-org/3.2/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.2
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.2.skip_if_unavailable=true
failure: repodata/repomd.xml from mongodb-org-3.2: [Errno 256] No more mirrors to try.
- duplicates
-
DOCS-7002 Comment on: "manual/tutorial/install-mongodb-on-amazon.txt"
- Closed
-
SERVER-21878 3.2 packages for amazon linux missing in official repository
- Closed