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...
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.
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
Are you trying to run this cluster on AWS?
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?
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.
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,
@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.
Hi rteague, I know this thread is really old, but I'm having this same error while trying to update CDH on my cluster. It is not part of AWS, but things seem to be ok until the socket timeoue. I tried adding the proxy to yum.conf, but it didn't seem to work. I am also able to connect to the scm through terminal with the script you posted