Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Failed to Install oracle-j2sdk1.7 on RHEL 7

Highlighted

Failed to Install oracle-j2sdk1.7 on RHEL 7

New Contributor

Hello,

I am trying to learn Cloudera CM,CDH, CM 5.16.1 have been installed successfully by rpms, now getting error on CDH 5.16.1 installation, Server have no internet access, rpm oracle-j2sdk1.7-1.7.0+update67-1.x86_64 has already been installed on both CM & CDH servers.

 

BEGIN yum --disablerepo=* --enablerepo=cloudera* clean all
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
: manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Cleaning repos: cloudera-manager
END (0)
BEGIN rm -Rf /var/cache/yum/x86_64
END (0)
BEGIN yum --disablerepo=* --enablerepo=cloudera* makecache
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
: manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.16.1/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: archive.cloudera.com; Unknown error"
Trying other mirror.


One of the configured repositories failed (Cloudera Manager, Version 5.16.1),
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=cloudera-manager ...

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 cloudera-manager
or
subscription-manager repos --disable=cloudera-manager

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=cloudera-manager.skip_if_unavailable=true

failure: repodata/repomd.xml from cloudera-manager: [Errno 256] No more mirrors to try.
https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.16.1/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: archive.cloudera.com; Unknown error"
END (1)