Reply
New Contributor
Posts: 1
Registered: ‎07-19-2016

CDH 5.7 installation stuck at Activation

I'm trying to install CDH in a two node cluster using

 

wget https://archive.cloudera.com/cm5/installer/latest/cloudera-manager-installer.bin

 

But it's stuck at activation for one of them.

 

stuck.JPG

When I checked /var/log/cloudera-scm-agent.log, I see this:

URLError: <urlopen error [Errno -2] Name or service not known>
[19/Jul/2016 10:29:40 +0000] 4276 Thread-13 downloader ERROR Failed fetching torrent: <urlopen error [Errno -2] Name or service not known>
Traceback (most recent call last):
File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.7.1-py2.7.egg/cmf/downloader.py", line 263, in download
cmf.https.ssl_url_opener.fetch_to_file(torrent_url, torrent_file)
File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.7.1-py2.7.egg/cmf/https.py", line 176, in fetch_to_file
resp = self.open(req_url)
File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.7.1-py2.7.egg/cmf/https.py", line 171, in open
return self.opener(*pargs, **kwargs)
File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 404, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 422, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 1214, in http_open
return self.do_open(httplib.HTTPConnection, req)
File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open
raise URLError(err)
URLError: <urlopen error [Errno -2] Name or service not known>

 

 

I chose all the defaults while installing using Cloudera Manager. How can I fix this? Thanks in advance.

Explorer
Posts: 7
Registered: ‎12-20-2016

Re: CDH 5.7 installation stuck at Activation

I am also having similar issue.


I'm trying to add a new node (CentOS 7.2) to my existing cluster which has CentOS 6.7. While going through the 'Add New Host Cluster' Wizard, activation of CDH parcel is stuck with 404: Not Found Error (below):


[06/Apr/2017 18:08:22 +0000] 32130 Thread-13 downloader ERROR Failed fetching torrent: HTTP Error 404: Not Found
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/downloader.py", line 263, in download
cmf.https.ssl_url_opener.fetch_to_file(torrent_url, torrent_file)
File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/https.py", line 175, in fetch_to_file
resp = self.open(req_url)
File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/https.py", line 170, in open
return self.opener(*pargs, **kwargs)
File "/usr/lib64/python2.7/urllib2.py", line 154, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib64/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
File "/usr/lib64/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib64/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/https.py", line 205, in http_error_default
raise e
HTTPError: HTTP Error 404: Not Found

Any solutions or workaround for this?

Thanks!

Cloudera Employee
Posts: 13
Registered: ‎04-21-2016

Re: CDH 5.7 installation stuck at Activation

This likely means that the host name of the CM server given to the agent does not resolve via DNS.

It may seem like a valid host name because it may be defined locally, but when we query a real DNS server we can't find it.

 

 

Posts: 749
Topics: 1
Kudos: 175
Solutions: 95
Registered: ‎04-22-2014

Re: CDH 5.7 installation stuck at Activation

@prakharpanwaria,

 

This error means that the agent attempted to download the the parcel torrent from Cloudera manager but the file does not exist.  When adding a CentOS 7.2 host, to your cluster, the agent will attempt to download the "EL7" parcel from Cloudera Manager.  In this case, it does not exist, so you get the 404 error.

 

Make sure that you have access to the correct remote parcel directory where the parcel can be downloaded.  For instance:

 

http://archive.cloudera.com/cdh5/parcels/5.10.0/

 

If that is configured properly, then Cloudera Manager should be able to download the necessary parcel so it is stored in /opt/cloudera/parcel-repo directory.

 

Check there to make sure the CDH-5.10.0-1.cdh5.10.0.p0.41-el7.parcel file exists.

 

-Ben

 

Posts: 749
Topics: 1
Kudos: 175
Solutions: 95
Registered: ‎04-22-2014

Re: CDH 5.7 installation stuck at Activation

Note that this is a much different issue than the original post.  Please start a new thread for the error 404 issue

Explorer
Posts: 7
Registered: ‎12-20-2016

Re: CDH 5.7 installation stuck at Activation

Thanks, it worked!

Highlighted
New Contributor
Posts: 2
Registered: ‎09-24-2017

Re: CDH 5.7 installation stuck at Activation

This error occurs, when you have hive replication/ hdfs replication running in you cluster.

 

To avoid this, stop any hive/hdfs replication commands CM---> Running commands (on the top right [left Search bar]).

 

Hope this helps!

Announcements