Reply
Highlighted
ash
Explorer
Posts: 7
Registered: ‎09-12-2013

Failed to detect Cloudera Manager Server

Hello,

I am trying to start a cluster of 5 nodes through cloudera manager 4.7.1. I am getting the following error on all the nodes.

 

Detecting Cloudera Manager Server...

CentOS release 6.2 (Final)
BEGIN host -t PTR 10.30.97.235
235.97.30.10.in-addr.arpa domain name pointer qfab-spade.imb.uq.edu.au.
END (0)
using qfab-spade.imb.uq.edu.au 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();' qfab-spade.imb.uq.edu.au 7182
/usr/bin/python
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 1, in connect
socket.timeout: timed out
END (1)
could not contact scm server at qfab-spade.imb.uq.edu.au:7182, giving up
waiting for rollback request
 

I have nodes accessible with passwordless ssh. my user has passwordless sudo permissions. My firewall and SELINUX are disabled in all the nodes. I found a few posts on google groups. But I coudnt find appropriate solutions.

 

I hope someone her can me suggest me something.

 

Thanks,

Ashwin

Cloudera Employee
Posts: 430
Registered: ‎09-27-2013

Re: Failed to detect Cloudera Manager Server

Hi Ashwin, it appears as if this agent cannot connect to your CM server qfab-spade.imb.uq.edu.au on port 7182.  Can you connect to port 7182 on qfab-spade.imb.uq.edu.au from this agent using the following command?

 

echo "quit" | nc -v localhost 7182

 

Also make sure Cloudera Manager Server is listening on port 7182 on qfab-spade.imb.uq.edu.au.

 

fuser -n tcp 7182
7182/tcp: 2442

Are you trying to run this cluster on AWS?

 

-roland

 

Cloudera Employee
Posts: 430
Registered: ‎09-27-2013

Re: Failed to detect Cloudera Manager Server

Sorry that command was supposed to be...

echo "quit" | nc -v qfab-spade.imb.uq.edu.au 7182
ash
Explorer
Posts: 7
Registered: ‎09-12-2013

Re: Failed to detect Cloudera Manager Server

Hello Roland,

 

Thanks for replying back to me. I am trying to create cluster not on AWS

 

But I have fixed that error. I was behind proxy. I tried export http_proxy to env but it didnt work. So I edited /etc/yum.conf and added my proxy details in that. And now I have got past that error. Now I am running into some warnings in the host inpector. Can we discuss this in the same thread or do I have to start a new one?

 

Thanks again.

 

Ashwin

Cloudera Employee
Posts: 430
Registered: ‎09-27-2013

Re: Failed to detect Cloudera Manager Server

Yes - feel free to post your additional question to this thread.

 

-roland

New Contributor
Posts: 1
Registered: ‎10-29-2013

Re: Failed to detect Cloudera Manager Server

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 

Cloudera Employee
Posts: 35
Registered: ‎08-08-2013

Re: Failed to detect Cloudera Manager Server

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?
New Contributor
Posts: 3
Registered: ‎11-30-2013

Re: Failed to detect Cloudera Manager Server

Hi,

I am new to hadoop and tried to install cloudera manager this time, I got the same error like yours, it is like: could not find scm server etc.

I'd like to know what you did to edit /etc/yum.conf and add a proxy details in that. 

can copy and paste that part, so I can modify mine accordingly.

 

thanks,

 

Robin

New Contributor
Posts: 3
Registered: ‎11-30-2013

Re: Failed to detect Cloudera Manager Server

Hi,

I got the same error when I install hadoop manager and I am trying to do the same thing you did to fix this error.

However, I dont know what my 'http_proxy' should be. I am new to Hadoop.

Can you share with me the line you added to your yum.conf file?

 

thank you very much,

 

Robin

Posts: 416
Topics: 51
Kudos: 89
Solutions: 49
Registered: ‎06-26-2013

Re: Failed to detect Cloudera Manager Server

@robi this page details how to set up an HTTP proxy in your yum.conf file, however you will need to provide the specific values required by those properties.  In other words, the server, port, username and password will all be specific to your company network.  You can probably discover what they should be set to by contacting your network admin or looking in your Proxy settings of your web browser to see what your browser is using.  HTH.