[mongodb-user] Repo issues while installing MongoDB on RHEL 7.4

'Ernie Hershey' via mongodb-user

2018-01-10 22:58:02 UTC

Hi,

There aren't currently any repos or packages published to the
"7Workstation" directory that your system is trying to access. As a
workaround, you can replace "$releasever" in your mongodb-org-3.6.repo
file with "7" and you should be able to proceed.

I've opened a JIRA ticket to track the work of adding these directories -
https://jira.mongodb.org/browse/SERVER-32651. You can follow that for
updates or add additional detail if you'd like.

Ernie

Post by v***@gmail.com
Hi there,
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-red-hat/
OS is RHEL 7.4. I'm getting 404's and the occasional connection refused
-- "Failed connect to repo.mongodb.org:443; Connection refused". Any
[mongodb-org-3.6]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mong
odb-org/3.6/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-3.6.asc
Loaded plugins: downloadkvmonly-background, ibm-check-lotus-updates, ibm-
check-xorg-updates, ibm-repository, langpacks, post-transaction-actions,
refresh-packagekit,
: versionlock
Cleaning repos: RHEL-7-x86_64-crashplan RHEL-74-x86_64 RHEL-74-x86_64-ibm-updates
RHEL-74-x86_64-updates mongodb-org-3.6
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by
orphaned data from disabled or removed repos
Loaded plugins: downloadkvmonly-background, ibm-check-lotus-updates, ibm-
check-xorg-updates, ibm-repository, langpacks, post-transaction-actions,
refresh-packagekit,
: versionlock
RHEL-7-x86_64-crashplan
| 2.9 kB 00:00:00
RHEL-74-x86_64
| 4.1 kB 00:00:00
RHEL-74-x86_64-ibm-updates
| 3.3 kB 00:00:00
RHEL-74-x86_64-updates
| 3.3 kB 00:00:00
https://repo.mongodb.org/yum/redhat/7Workstation/mongodb-org
/3.6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please open a ticket
with Red Hat Support.
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. Run the command with the repository temporarily disabled
yum --disablerepo=mongodb-org-3.6 ...
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
yum-config-manager --disable mongodb-org-3.6
or
subscription-manager repos --disable=mongodb-org-3.6
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
yum-config-manager --save --setopt=mongodb-org-3.6.skip_
if_unavailable=true
failure: repodata/repomd.xml from mongodb-org-3.6: [Errno 256] No more
mirrors to try.
https://repo.mongodb.org/yum/redhat/7Workstation/mongodb-org
/3.6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Loaded plugins: downloadkvmonly-background, ibm-check-lotus-updates,
ibm-check-xorg-updates, ibm-repository, langpacks,
post-transaction-actions, refresh-packagekit,
: versionlock
RHEL-7-x86_64-crashplan
| 2.9 kB 00:00:00
RHEL-74-x86_64
|
4.1 kB 00:00:00
RHEL-74-x86_64-ibm-updates
|
3.3 kB 00:00:00
RHEL-74-x86_64-updates
|
3.3 kB 00:00:00
https://repo.mongodb.org/yum/redhat/7Workstation/mongodb-org
/3.6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please open a ticket
with Red Hat Support.
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. Run the command with the repository temporarily disabled
yum --disablerepo=mongodb-org-3.6 ...
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
yum-config-manager --disable mongodb-org-3.6
or
subscription-manager repos --disable=mongodb-org-3.6
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
yum-config-manager --save --setopt=mongodb-org-3.6.skip_
if_unavailable=true
failure: repodata/repomd.xml from mongodb-org-3.6: [Errno 256] No more
mirrors to try.
https://repo.mongodb.org/yum/redhat/7Workstation/mongodb-org
/3.6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
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
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/mongodb-user/98b2b54e-f3e7-4bb0-a9ca-44d971af21e2%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/98b2b54e-f3e7-4bb0-a9ca-44d971af21e2%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

--
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/CANz8sXyHYXC1MR6ZZqaXuByeDg4w%2BgNc%3DAOEPF3uhxFMiGdcEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.