Reply
New Contributor
Posts: 1
Registered: ‎12-24-2016

Deploying CDH 5.9.0/ZooKeeper via parcels on CentOS 7.x localrepo

Hi

 

Testing a deployment of CM 5.9.0 and CDH 5.9.0 on Virtualbox with the CM RPM's and CDH parcels on a localrepo, error is as follows;

 

/tmp/scm_prepare_node.jU2qznl7
using SSH_CLIENT to get the SCM hostname: 192.168.43.103 56070 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 'CentOS release 5' /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
END (1)
BEGIN grep 'CentOS Linux release 7' /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)
END (0)
/etc/redhat-release ==> CentOS 7
Detecting Cloudera Manager Server...
BEGIN host -t PTR 192.168.43.103
;; connection timed out; no servers could be reached
END (1)
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();' 192.168.43.103 7182
END (0)
BEGIN which wget
which: no wget in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin)
END (1)
BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest/meta-data/public-hostname && /bin/echo
END (127)
/tmp/scm_prepare_node.jU2qznl7/scm_prepare_node.sh: line 105: wget: command not found
Installing package repositories...
validating format of repository file /tmp/scm_prepare_node.jU2qznl7/repos/rhel7/cloudera-manager.repo
installing repository file /tmp/scm_prepare_node.jU2qznl7/repos/rhel7/cloudera-manager.repo
repository file /tmp/scm_prepare_node.jU2qznl7/repos/rhel7/cloudera-manager.repo installed
Refreshing package metadata...
BEGIN yum clean all
Loaded plugins: fastestmirror
Cleaning repos: c7-media cloudera-cdh5 cloudera-cm cloudera-manager
Cleaning up everything
END (0)
BEGIN rm -Rf /var/cache/yum/x86_64
END (0)
BEGIN yum makecache
Loaded plugins: fastestmirror
https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.9.0/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.9.0),
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 cloudera-manager

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=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.9.0/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: archive.cloudera.com; Unknown error"
END (1) 

 
Also attached below a copy of my /etc/yum.repos.d/ configuration for the localrepos
 
[cloudera-cdh5]
# Packages for Cloudera's Distribution for Hadoop, Version 5, on RedHat	or CentOS 7 x86_64
name=Cloudera's Distribution for Hadoop, Version 5
baseurl=http://192.168.43.103/cdh5/latest/
#	http://192.168.43.103/cm/latest/
#gpgkey =https://archive.cloudera.com/cdh5/redhat/7/x86_64/cdh/RPM-GPG-KEY-cloudera    
#gpgcheck = 0
enabled = 1
[cloudera-manager]
name = Cloudera Manager, Version 5.9.0
baseurl = http://192.168.43.103/cm/latest/
#gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
#gpgcheck = 0
enabled = 1
[cloudera-cm]
name = Cloudera's Distribution for cm, Version 5.9.0
baseurl = http://192.168.43.103/cm/latest/
gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
gpgcheck = 0
enabled=1
Also to note, the cloudera-manager always reverts back to it's defaults when the it fails and I vi back into the file.
 
Any thoughts? very odd? Previous cluster configured against CentOS 6.x and CDH and CM 5.8.x with localrepo with no issues.
Posts: 1,044
Topics: 1
Kudos: 262
Solutions: 130
Registered: ‎04-22-2014

Re: Deploying CDH 5.9.0/ZooKeeper via parcels on CentOS 7.x localrepo

Based on what you said, since you are using a custom repository and the install wizard, you can specify your custom repository in the following screen:

 

Select the specific release of the Cloudera Manager Agent you want to install on your hosts.

-Matched release for this Cloudera Manager Server
-Custom Repository
 
You can select "Custom Repository" and then enter in the URLs for your custom repository.
When Cloudera Manager tries to install the packages on your host, it will copy over the repo information for use in yum on each host.
 
Regards,
 
Ben
Announcements