Cloudera Community
asterix
user rank
Explorer
My Accepted Solutions
Show All

Re: Cluster installation - The inspector failed to...

by Explorer in Support Questions
‎02-14-2016 05:49 AM
‎02-14-2016 05:49 AM
Hi,    I was interested in this threat since I encountered similar issues in a simple cluster config. I'm using CM5 on CentOS 7.2 The host inspector gave : master1.domain; worker[1-3].domain: IOException thrown while collecting data from host: Connection refused The point is that each hosts is using a public IP address on eth0 and a private IP address on eth1. As you can guess, I want my cluster to use the internal IP only. I tried several things (between each stage, I restarted cloudera-scm-agent to make sure the modification is taken into account)   1- I tried to make some modifications to my /etc/hosts to precise public FQDN for public IP ==> FAIL 2 - I tried to use /etc/cloudera-scm/agent/config.ini , listening_ip to listen ONLY on the private IP ==> FAIL 3 - I tried to use /etc/cloudera-scm/agent/config.ini , listening_hostname to listen ONLY on the hostname associated with the private interface ==> FAIL.  At this stage, I can say, Cloudera agent is listening only on private interface (lsof confirmed) bue the inspector does not seem to focus on this 4 - I shut down eth0 (public interface) to disable multiple hostnames  ==> SUCCESS   At this stage, I wondered why 3 fails and 4 succeeded. I think this is due to the python script below used to detect the hostname instead of using the cloudera config file :   python -c 'import socket; \               print socket.getfqdn(), \                     socket.gethostbyname(socket.getfqdn())'   This script seem to give the fqdn for eth0 first so no luck for me. Not sure this is the solution but the trick worked for me. It could make sense if Cloudera staff review the inspector code and make sure python code know how to use the config file.         ... View more

Re: urlopen on parcels installation

by Explorer in Support Questions
‎02-10-2016 07:30 AM
‎02-10-2016 07:30 AM
Hi @cjervis,   Thank you for your proposal. I checked the thread you mentionned when I got the issue but it's not related to my case. I tried to restart the agent with sudo as mentionned by the author but it didn't work.       Your post forced me to replay all the steps and I found the answer so I share to avoid an other beginner to find in this hole :   the hostname for the cloudera-server was initially configured as a public FQDN. After that, I changed it with an internal FQDN and all the other internal DNS stuff, but cloudera manager kept continuing to share this public IP with its agent but the firewall was blocking the trafic.   I found this in the download field of the agent log where the public FQDN was mentioned. I just had to restart everything and now it seems to be ok.   Thank you very much for your tip   ... View more

Re: urlopen on parcels installation

by Explorer in Support Questions
‎02-10-2016 03:24 AM
‎02-10-2016 03:24 AM
I tried several things but none was successful and I couldn't find an answer in the community. I feel alone...   Someone who could have an idea ?     ... View more

urlopen on parcels installation

by Explorer in Support Questions
‎02-05-2016 03:19 PM
‎02-05-2016 03:19 PM
Hi all,   I'm a new Cloudera user, I'm installing a small cluster of CDH-5-5.1.11 on different hosts on Cent OS 7.2. In the automatic process, during parcel installation stage, I get "urlopen error timed out" on all hosts excepted the CLoudera manager server. Everything has been checked (firewall is ok, files can be downloaded on the hosts directly from the internet or from the manager with direct curl). I can't find a relevant solution on the forum.   Any ideas   Details below :   - part files stay at 0 in the cache directory on the hosts  - cloudera agent log file gives : [06/Feb/2016 00:16:04 +0000] 11288 Thread-13 downloader   INFO     Starting download of: http://gw.domain.com:7180/cmf/parcel/download/CDH-5.5.1-1.cdh5.5.1.p0.11-el7.parcel [06/Feb/2016 00:16:04 +0000] 11288 Thread-13 downloader   INFO     /opt/cloudera/parcel-cache/CDH-5.5.1-1.cdh5.5.1.p0.11-el7.parcel.part exists, add Range header: bytes=0- [06/Feb/2016 00:16:34 +0000] 11288 Thread-13 downloader   ERROR    Unexpected exception during download Traceback (most recent call last):   File "/usr/lib64/cmf/agent/src/cmf/downloader.py", line 276, in _download     response = self.opener.fetch_url(request)   File "/usr/lib64/cmf/agent/src/cmf/downloader.py", line 69, in fetch_url     return urllib2.urlopen(request)   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 431, in open     response = self._open(req, data)   File "/usr/lib64/python2.7/urllib2.py", line 449, in _open     '_open', req)   File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain     result = func(*args)   File "/usr/lib64/python2.7/urllib2.py", line 1244, in http_open     return self.do_open(httplib.HTTPConnection, req)   File "/usr/lib64/python2.7/urllib2.py", line 1214, in do_open     raise URLError(err) URLError: <urlopen error timed out> [06/Feb/2016 00:16:34 +0000] 11288 Thread-13 downloader   INFO     Finished download [ url: http://gw.domain.com:7180/cmf/parcel/download/CDH-5.5.1-1.cdh5.5.1.p0.11-el7.parcel, state: exception, total_bytes: 0, downloaded_bytes: 0, start_time: 2016-02-06 00:16:04, download_end_time: , end_time: 2016-02-06 00:16:34, code: 600, exception_msg: <urlopen error timed out>, path: None ]   ... View more
Contact Me
Online
Offline
Last Visited
‎06-20-2017 07:30 AM
Community Statistics
Member Since ‎02-05-2016 02:48 PM
Last Visited ‎06-20-2017 07:30 AM
Posts 5