Discussion:
Mongodb repo down?
(too old to reply)
Stephen Knight
2016-04-05 07:00:31 UTC
Permalink
Guys,

It seems the Mongo repos are broken this morning, has anyone else had the
same problem?

Error from my CentOS boxes during install:

https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/repodata/2a7391c733c8867a5d7ed76397bea55208ffee52-primary.sqlite.bz2:
[Errno 14] HTTPS 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/2a7391c733c8867a5d7ed76397bea55208ffee52-primary.sqlite.bz2
from mongodb-org-3.0: [Errno 256] No more mirrors to try.
https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.0/x86_64/repodata/2a7391c733c8867a5d7ed76397bea55208ffee52-primary.sqlite.bz2:
[Errno 14] HTTPS Error 404 - Not Found

Checking the repomd.xml is references the xxx.primary.sql.bz2 as above
which doesn't exist in repodata on the server.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/7a43f769-284c-4524-b758-f10121089e1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Oscar Esteve
2016-04-05 10:13:43 UTC
Permalink
+1
Post by Stephen Knight
Guys,
It seems the Mongo repos are broken this morning, has anyone else had the
same problem?
https://
[Errno 14] HTTPS 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
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
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
yum-config-manager --save --setopt=mongodb-org-3.0.
skip_if_unavailable=true
failure: repodata/2a7391c733c8867a5d7ed76397bea55208ffee52-primary.sqlite.bz2
from mongodb-org-3.0: [Errno 256] No more mirrors to try.
https://
[Errno 14] HTTPS Error 404 - Not Found
Checking the repomd.xml is references the xxx.primary.sql.bz2 as above
which doesn't exist in repodata on the server.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/cf869ffa-8d91-4fe9-a7b3-14f91fdef17d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Peter Howells
2016-04-05 10:02:23 UTC
Permalink
Same issue here with 3.2:

https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.2/x86_64/repodata/3a8dbf4e974179f2d063acb5bfde9c502961fdd6-primary.sqlite.bz2:
[Errno 14] HTTPS Error 404 - Not Found
Post by Stephen Knight
Guys,
It seems the Mongo repos are broken this morning, has anyone else had the
same problem?
https://
[Errno 14] HTTPS 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
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
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
yum-config-manager --save --setopt=mongodb-org-3.0.
skip_if_unavailable=true
failure: repodata/2a7391c733c8867a5d7ed76397bea55208ffee52-primary.sqlite.bz2
from mongodb-org-3.0: [Errno 256] No more mirrors to try.
https://
[Errno 14] HTTPS Error 404 - Not Found
Checking the repomd.xml is references the xxx.primary.sql.bz2 as above
which doesn't exist in repodata on the server.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/d049ddcb-d50f-4fc3-9cfc-054aa20bc073%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
m***@gmail.com
2016-04-05 08:10:48 UTC
Permalink
Same for me :( yum clean all && yum makecache gives me:

mongodb

| 2.5 kB 00:00
http://repo.mongodb.org/yum/redhat/6/mongodb-org/3.0/x86_64/repodata/c4bdec78737c3facddf5fe8d5ee760aa6884aa85-filelists.sqlite.bz2:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"
Trying other mirror.
http://repo.mongodb.org/yum/redhat/6/mongodb-org/3.0/x86_64/repodata/052a7772f29b4279f44b71a0e1137010ce138ada-primary.sqlite.bz2:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"
Trying other mirror.
Error: failure:
repodata/052a7772f29b4279f44b71a0e1137010ce138ada-primary.sqlite.bz2 from
mongodb: [Errno 256] No more mirrors to try.


Thanks,
Marcin
Post by Stephen Knight
Guys,
It seems the Mongo repos are broken this morning, has anyone else had the
same problem?
https://
[Errno 14] HTTPS 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
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
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
yum-config-manager --save --setopt=mongodb-org-3.0.
skip_if_unavailable=true
failure: repodata/2a7391c733c8867a5d7ed76397bea55208ffee52-primary.sqlite.bz2
from mongodb-org-3.0: [Errno 256] No more mirrors to try.
https://
[Errno 14] HTTPS Error 404 - Not Found
Checking the repomd.xml is references the xxx.primary.sql.bz2 as above
which doesn't exist in repodata on the server.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/78da013b-e6d4-49b4-81aa-97380ba3043b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Stephen Steneker
2016-04-05 10:22:10 UTC
Permalink
Hi All,

Thanks for the reports .. we're looking into the repo issue and will update
this discussion when there's a fix.

Regards,
Stephen
Post by Stephen Knight
mongodb
| 2.5 kB 00:00
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"
Trying other mirror.
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"
Trying other mirror.
repodata/052a7772f29b4279f44b71a0e1137010ce138ada-primary.sqlite.bz2 from
mongodb: [Errno 256] No more mirrors to try.
Thanks,
Marcin
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/9e5c4b5e-649f-4596-a4ad-c595b201a3fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Stephen Steneker
2016-04-05 11:27:32 UTC
Permalink
Post by Stephen Steneker
Thanks for the reports .. we're looking into the repo issue and will
update this discussion when there's a fix.
Hi All,

We've regenerated the repo metadata and it should be working fine now. It
may take up to 30 minutes for the CDN cache to refresh.

Regards,
Stephen
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/9ec884b8-3168-465d-9ee9-70a0df727581%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Ian Sharp
2016-04-14 18:14:25 UTC
Permalink
Hi, i'm also getting this today (april 14th)

failure: repodata/repomd.xml from mongodb-org-3.0: [Errno 256] No more
mirrors to try.


from
$ sudo yum install mongodb-org
Post by Stephen Steneker
Post by Stephen Steneker
Thanks for the reports .. we're looking into the repo issue and will
update this discussion when there's a fix.
Hi All,
We've regenerated the repo metadata and it should be working fine now. It
may take up to 30 minutes for the CDN cache to refresh.
Regards,
Stephen
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/69a3f4a7-0a55-4b4b-9fff-b4e66809728c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wan Bachtiar
2016-04-15 08:15:47 UTC
Permalink
failure: repodata/repomd.xml from mongodb-org-3.0: [Errno 256] No more
mirrors to try.

Hi Ian,

I’ve just tested this on RHEL7 (As mentioned on the original post), and by
following the installation steps Install MongoDB on Amazon
<https://docs.mongodb.org/v3.2/tutorial/install-mongodb-on-amazon/#install-mongodb>
it works without any issues (v3.0.x and v3.2.x).

You may also be interested to check out: Why does yum return error: No more
mirrors to try <https://access.redhat.com/solutions/203603>

If you still have difficulties on installing MongoDB, can you provide the
following:

- Specific Operating Systems and version
- The installation steps that you did
- The content of your mongodb repo file
- The full error message that you are getting

Regards,

Wan.
​
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/970a382e-c61f-422e-b8f7-8ce635f31b47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
b***@sentinelone.com
2016-09-18 20:19:02 UTC
Permalink
Hi Guys,

It seems this error is back.
Post by Ian Sharp
failure: repodata/repomd.xml from mongodb-org-3.0: [Errno 256] No more
mirrors to try.
Hi Ian,
I’ve just tested this on RHEL7 (As mentioned on the original post), and by
following the installation steps Install MongoDB on Amazon
<https://docs.mongodb.org/v3.2/tutorial/install-mongodb-on-amazon/#install-mongodb>
it works without any issues (v3.0.x and v3.2.x).
You may also be interested to check out: Why does yum return error: No
more mirrors to try <https://access.redhat.com/solutions/203603>
If you still have difficulties on installing MongoDB, can you provide the
- Specific Operating Systems and version
- The installation steps that you did
- The content of your mongodb repo file
- The full error message that you are getting
Regards,
Wan.
​
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/4ec7bf3a-6679-4fc8-8f01-44050f256328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wan Bachtiar
2016-09-20 02:15:55 UTC
Permalink
It seems this error is back.

Hi,

I’ve tested the repo install for MongoDB v3.0 and v3.2 on CentOS 7 (RHL
based), via yum install -y mongodb-org with success.

If you still having issues installing MongoDB, could you please open a new
thread with the following information:

- Specific Operating Systems and version
- The installation steps that you did. See Install MongoDB v3.2 on Redhat
<https://docs.mongodb.com/manual/tutorial/install-mongodb-on-red-hat/>.
- The content of your mongodb .repo file
- The full error message that you are getting

Also as suggested previously, you may find useful : Why does yum return
error: No more mirrors to try <https://access.redhat.com/solutions/203603>

Regards,

Wan.

​
​
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/7843a53c-5ada-454f-a9f2-3f74bae83791%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Continue reading on narkive:
Loading...