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.

Problem in creating cloudera cluster

Solved Go to solution

Problem in creating cloudera cluster

Rising Star

I am building a cluster with 3 nodes. the cloudera manager is able to successfully install everything on 2 nodes but one of them fails

 

capture.png

When I click on details I can see

 

Configuring Cloudera Manager Agent...

BEGIN grep server_host=155.17.148.40 /etc/cloudera-scm-agent/config.ini
END (1)
BEGIN sed -e 's/\(server_host=\).*/\1155.17.148.40/' -i /etc/cloudera-scm-agent/config.ini
END (0)
scm agent configured

Starting Cloudera Manager Agent...

BEGIN /sbin/service cloudera-scm-agent status | grep running
END (1)
BEGIN /sbin/service cloudera-scm-agent start
Starting cloudera-scm-agent: [FAILED]
END (1)
agent logs:
BEGIN tail -n 50 /var/log/cloudera-scm-agent//cloudera-scm-agent.out | sed 's/^/>>/'
>>/usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
>> import sha
>>/usr/lib64/cmf/agent/src/cmf/parcel.py:15: DeprecationWarning: the sets module is deprecated
>> from sets import Set
>>[17/Dec/2014 14:13:31 +0000] 9557 MainThread agent INFO SCM Agent Version: 5.2.1
>>[17/Dec/2014 14:13:31 +0000] 9557 MainThread agent ERROR Could not determine hostname or ip address; proceeding.
>>Traceback (most recent call last):
>> File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1854, in parse_arguments
>> ip_address = socket.gethostbyname(fqdn)
>>gaierror: [Errno -3] Temporary failure in name resolution
>>usage: agent.py [-h] [--agent_dir AGENT_DIR

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Problem in creating cloudera cluster

Rising Star

OK. I resolved the problem.

 

on hd3work the call to 

 

 python -c 'import socket; socket.gethostbyname(socket.getfqdn())

 

was failing.

 

I troubleshooted for a very long time and could not figure out why this problem is occuring.

 

so I deleted the network adapter of the VM and recreated the network adapter.

 

then suddenly it started to work.

 

2 REPLIES 2

Re: Problem in creating cloudera cluster

Rising Star

This is my cloudera-scm-agent.out file

 

/usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha
/usr/lib64/cmf/agent/src/cmf/parcel.py:15: DeprecationWarning: the sets module is deprecated
from sets import Set
[17/Dec/2014 14:19:52 +0000] 9985 MainThread agent INFO SCM Agent Version: 5.2.1
[17/Dec/2014 14:19:52 +0000] 9985 MainThread agent ERROR Could not determine hostname or ip address; proceeding.
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1854, in parse_arguments
ip_address = socket.gethostbyname(fqdn)
gaierror: [Errno -3] Temporary failure in name resolution
usage: agent.py [-h] [--agent_dir AGENT_DIR] [--lib_dir LIB_DIR]
[--agent_httpd_port AGENT_HTTPD_PORT] --package_dir
PACKAGE_DIR [--parcel_dir PARCEL_DIR]
[--supervisord_path SUPERVISORD_PATH]
[--supervisord_httpd_port SUPERVISORD_HTTPD_PORT]
[--standalone STANDALONE] [--master MASTER]
[--environment ENVIRONMENT] [--host_id HOST_ID]
[--disable_supervisord_events] --hostname HOSTNAME
--ip_address IP_ADDRESS [--use_tls]
[--client_key_file CLIENT_KEY_FILE]
[--client_cert_file CLIENT_CERT_FILE]
[--verify_cert_file VERIFY_CERT_FILE]
[--verify_cert_dir VERIFY_CERT_DIR]
[--client_keypw_file CLIENT_KEYPW_FILE]
[--max_cert_depth MAX_CERT_DEPTH] [--logfile LOGFILE]
[--logdir LOGDIR] [--optional_token] [--clear_agent_dir]
[--sudo_command SUDO_COMMAND]
agent.py: error: argument --hostname is required
[17/Dec/2014 14:19:52 +0000] 9985 Dummy-1 agent INFO Stopping agent...

Highlighted

Re: Problem in creating cloudera cluster

Rising Star

OK. I resolved the problem.

 

on hd3work the call to 

 

 python -c 'import socket; socket.gethostbyname(socket.getfqdn())

 

was failing.

 

I troubleshooted for a very long time and could not figure out why this problem is occuring.

 

so I deleted the network adapter of the VM and recreated the network adapter.

 

then suddenly it started to work.

 

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