Mongodb repo down?

[Stephen Knight]

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.

[Peter Howells]

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

[Oscar Esteve]

+1

[m.j...@gmail.com]

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

[Stephen Steneker]

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

[Stephen Steneker]

On Tuesday, 5 April 2016 20:22:10 UTC+10, Stephen Steneker wrote:

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

[Ian Sharp]

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

[Wan Bachtiar]

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 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

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.

​

[bo...@sentinelone.com]

Hi Guys,

It seems this error is back.

[Wan Bachtiar]

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.
• 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

Regards,

Wan.

​

​

[Haminou M.]

Hi guys,

 

is the repo broken again?

I just tried installing the version 4.0 on amazon linux 2 and received the following error message:

Loaded plugins: extras_suggestions, langpacks, priorities, update-motd

https://repo.mongodb.org/yum/amazon/2/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.mongodb.org/yum/amazon/2/mongodb-org/4.0/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 5001 milliseconds')

Trying other mirror.

https://repo.mongodb.org/yum/amazon/2/mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.mongodb.org/yum/amazon/2/mongodb-org/4.0/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 5001 milliseconds')

Trying other mirror.

^C

 Current download cancelled, interrupt (ctrl-c) again within two seconds

to exit.

 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. Run the command with the repository temporarily disabled

            yum --disablerepo=mongodb-org-4.0 ...

     4. Disable the repository permanently, 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-4.0

        or

            subscription-manager repos --disable=mongodb-org-4.0

     5. 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-4.0.skip_if_unavailable=true

[Matt Lord]

Hi Haminou,

Are you still encountering the issue? It seems to be ok right now, and I'm not on any corporate network:

$ wget https://repo.mongodb.org/yum/amazon/2/mongodb-org/4.0/x86_64/repodata/repomd.xml
--2018-12-22 11:58:08-- https://repo.mongodb.org/yum/amazon/2/mongodb-org/4.0/x86_64/repodata/repomd.xml
Resolving repo.mongodb.org (repo.mongodb.org)... 52.85.105.18
Connecting to repo.mongodb.org (repo.mongodb.org)|52.85.105.18|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2510 (2.5K) [text/xml]
Saving to: ‘repomd.xml’
100%[=============================================================================================================================>] 2,510 10.8KB/s in 0.2s
2018-12-22 11:58:09 (10.8 KB/s) - ‘repomd.xml’ saved [2510/2510]


I wonder if you're encountering a bad switch/router in your current network route? You can try and look for that this way:
$ mtr -r repo.mongodb.org

Best Regards

Matt

[Haminou M.]

Hi Matt,

thanks the proxy settings was wrong. Using the mtr -r command helped me!