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.

Failed to detect Cloudera Manager Server

Highlighted

Re: Failed to detect Cloudera Manager Server

New Contributor

hi, I have the similar problem, plz help!

 

The different is my cluster use /etc/hosts to resolve hostname

/etc/hosts contain such content:

192.168.0.55 VM-N1
192.168.0.56 VM-N2
192.168.0.57 VM-N3

 

And cloudera-manager-server is  installed on VM-N2,  the nodes use the same username(root) and password to ssh.

But the installation wizard  can  only install VM-N2 successfully, the other nodes always report error when "Detecting Cloudera Manager Server..".

 

I make sure

(1) the server is running:

$service cloudera-scm-server status
cloudera-scm-server (pid  8011) is running...

 

(2)

echo "quit" | nc -v localhost 7182
nc: connect to localhost port 7182 (tcp) failed: Connection refused
Connection to localhost 7182 port [tcp/*] succeeded!
HTTP/1.1 400 Bad Request
Connection: close
Server: Jetty(6.1.26.cloudera.2)

 

(3) and I run this script in shell

 

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();' localhost 7182 

 

it does not echo error

 

 

 

 

 

Red Hat Enterprise Linux Server release 6.3 (Santiago) 
BEGIN host -t PTR 192.168.0.56 
56.0.168.192.in-addr.arpa domain name pointer localhost. 
END (0) 
using localhost as scm server hostname 
BEGIN which 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();' localhost 7182 
/usr/bin/python 
Traceback (most recent call last): 
File "<string>", line 1, in <module> 
File "<string>", line 1, in connect 
socket.error: [Errno 111] Connection refused 
END (1) 
could not contact scm server at localhost:7182, giving up 
waiting for rollback request 

Re: Failed to detect Cloudera Manager Server

Contributor
Seems that the FQDN of VM-N2 is "localhost". Let's verify -- Can you go to VM-N3, and run `grep server_host /etc/cloudera-scm-agent/config.ini'?

If it says `localhost', then your VM-N2 has an ip address that resolves back to `localhost', which means that the rest of the cluster will not be able to talk to VM-N2 properly.

Try this on VM-N3: `host -t PTR 192.168.0.56'. What does it say?

Can you double-check your /etc/hosts again?
Highlighted

Re: Failed to detect Cloudera Manager Server

New Contributor

i also faced the similar issue, when worked with IT support team get to know that issue is with server on which cloudera is being installed(Master server). DNS entry need to removed which it trying to get details of scm server.

hope this helps.

 

Cheers,
Ankit

 

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