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.

Cloudera 6.1.1 installation issue

Highlighted

Cloudera 6.1.1 installation issue

New Contributor

Hi Team,

 

While trying to install cloudera 6.1.1

In the install agent step everytime it is giving an error --- "can not find the base url for cloudera manager" .  On every  restart  of that step it is downloading the cloudera.repo file which is empty and not having base url and gpg key from the server.

 

Kindly help as I am struck here from long time

 

error message:

/tmp/scm_prepare_node.dxa752zO
using SSH_CLIENT to get the SCM hostname: 10.40.158.194 52498 22
opening logging file descriptor

Starting installation script...

Acquiring installation lock...

BEGIN flock 4
END (0)

Detecting root privileges...

effective UID is 0

Detecting distribution...

BEGIN grep Tikanga /etc/redhat-release
END (1)
BEGIN grep 'Scientific Linux release 5' /etc/redhat-release
END (1)
BEGIN grep Santiago /etc/redhat-release
END (1)
BEGIN grep 'CentOS Linux release 6' /etc/redhat-release
END (1)
BEGIN grep 'CentOS release 6' /etc/redhat-release
END (1)
BEGIN grep 'Scientific Linux release 6' /etc/redhat-release
END (1)
BEGIN grep Maipo /etc/redhat-release
Red Hat Enterprise Linux Server release 7.6 (Maipo)
END (0)
/etc/redhat-release ==> RHEL 7

Detecting Cloudera Manager Server...

BEGIN host -t PTR 10.40.158.194
194.158.40.10.in-addr.arpa domain name pointer whf00pjn.in.oracle.com.
END (0)
using whf00pjn.in.oracle.com as scm server hostname
BEGIN which python
/usr/bin/python
END (0)
BEGIN python -c 'import socket; import sys; s = socket.socket(socket.AF_INET); s.settimeout(5.0); s.connect((sys.argv[1], int(sys.argv[2]))); s.close();' whf00pjn.in.oracle.com 7182
END (0)
BEGIN which wget
/usr/bin/wget
END (0)
BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest/meta-data/public-hostname && /bin/echo
lrsnextgencluster2-server-240.novalocal
END (0)

Installing package repositories...

Checking https://archive.cloudera.com/cm6/6.1.1/redhat7/yum/repodata/repomd.xml
Checking https://archive.cloudera.com/cm6/6.1.1/repodata/repomd.xml
Using
installing repository file /tmp/scm_prepare_node.dxa752zO/repos/rhel7/cloudera-manager.repo
repository file /tmp/scm_prepare_node.dxa752zO/repos/rhel7/cloudera-manager.repo installed
installing rpm keys
BEGIN gpg --import /tmp/scm_prepare_node.dxa752zO/customGPG
gpg: keyring `/tmp/scm_prepare_node.dxa752zO/gnupg.gKxbmrVB0W/secring.gpg' created
gpg: keyring `/tmp/scm_prepare_node.dxa752zO/gnupg.gKxbmrVB0W/pubring.gpg' created
gpg: /tmp/scm_prepare_node.dxa752zO/gnupg.gKxbmrVB0W/trustdb.gpg: trustdb created
gpg: key 02A818DD: public key "Cloudera Apt Repository" imported
gpg: key E8F86ACD: public key "Yum Maintainer <webmaster@cloudera.com>" imported
gpg: key B0B19C9F: public key "Parameterized Build <security@cloudera.com>" imported
gpg: key 84415700: public key "Cloudera <security@cloudera.com>" imported
gpg: key 36F57F35: public key "Cloudera <security@cloudera.com>" imported
gpg: Total number processed: 5
gpg: imported: 5 (RSA: 3)
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.dxa752zO/F36A89E33CC1BD0F71079007327574EE02A818DD.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.dxa752zO/5F14D39EF0681ACA6F044A43F90C0D8FE8F86ACD.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.dxa752zO/9543951160C284C0E7CA254573985D43B0B19C9F.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.dxa752zO/CECDB80C4E9004B0CFE852962279662784415700.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.dxa752zO/DF2C4DD7629B1AC08A0966E00F65552736F57F35.pub
END (0)

Refreshing package metadata...

BEGIN yum --disablerepo=* --enablerepo=cloudera* clean all
Loaded plugins: fastestmirror, langpacks, ulninfo, versionlock
Cleaning repos: cloudera-manager
Cleaning up list of fastest mirrors
END (0)
BEGIN rm -Rf /var/cache/yum/x86_64
END (0)
BEGIN yum --disablerepo=* --enablerepo=cloudera* makecache
Loaded plugins: fastestmirror, langpacks, ulninfo, versionlock
Determining fastest mirrors


One of the configured repositories failed (Unknown),
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=<repoid> ...

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

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

Cannot find a valid baseurl for repo: cloudera-manager
END (1)

Installing cloudera-manager-agent package...

BEGIN yum --disablerepo=* --enablerepo=cloudera* list installed cloudera-manager-agent
Loaded plugins: fastestmirror, langpacks, ulninfo, versionlock
Error: No matching Packages to list
END (1)
BEGIN yum --disablerepo=* --enablerepo=cloudera* info cloudera-manager-agent
Loaded plugins: fastestmirror, langpacks, ulninfo, versionlock
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Unknown),
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=<repoid> ...

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

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

Cannot find a valid baseurl for repo: cloudera-manager
END (1)
cloudera-manager-agent must have Version=6.1.1 and Build=853290, exiting
closing logging file descripton
1 REPLY 1

Re: Cloudera 6.1.1 installation issue

Super Collaborator

Hi @Sneha,

 

It looks like you are using ssl (https) and you mentioned cloudera-manager.repo content is empty on the agent hosts. I wonder if the agent hosts do not have direct outbound access to internet?

 

There is an open bug that CM agent does not download key bundles when behind proxy with auth & SSL even you have configured the proxy setting in CM UI. I feel this may be the cause of the issue you are facing.

 

Could you please try this test and see if that helps to remedy the issue? Please try to pre-configure https_proxy in each CM agent host's bash environment. For example:

echo "https_proxy=http://yourproxyhost.com:3128" >> /etc/bashrc 
echo "no_proxy=*.your_internal_domain.com" >> /etc/bashrc

 

Thanks and hope this helps!

Li

 

 

Li Wang, Technical Solution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

Community Guidelines

How to use the forum

Don't have an account?
Coming from Hortonworks? Activate your account here