socket.error: [Errno 113] No route to host (Adding nodes to Cloudera Manager)

[#1]

Hello clouderians,

I am currently installing Cloudera Manager in a cluster of 6 hosts (all with CentOS 7.1).

When I try to add hosts to the cluster, their installation fail and the details are as show in the picture bellow.

Configurations:

 - The file /etc/hosts in every hosts have their IPs (all of each other) and names;

 - They all have root access throught ssh, with publickey, to each other.

 - The selinux is disabled (/etc/selinux/config);

 - The perl packet is installed;

Does anyone have any suggestions?

Thank you very much in advance!

António Eleutério

[#2]

I checked pings and they all are around 400ms. Could this be the case?

[#3]

I have the same problem ! Have you found a solution?

[#4]

chkconfig iptables off

chkconfig ip6tables off

service iptables stop

service iptables stop

vi  /etc/selinux/config

selinux= disabled

do the all the nodes and then restart the machin init 6

thats...the solution ............................kalyans.y

[#5]

chkconfig iptables stop

chkconfig ip6tasbles stop

[#6]

I am getting the same error message now. Kindly let me know if any solution

[#7]

@Sats,

There is no one solution for this.  In order for us to know that you have exactly the same condition, please share screen shots and logs that show what helps you determine that you are seeing an issue where the agent cannot heartbeat to Cloudera Manager after starting.

In the original post, the error was "no route to host".  This indicates problems in the network or the OS network configuration.

Before going further, we'll need to know what problem you observe to make sure our investigation and help is targted on the right issue.

Thanks,

Ben

[#8]

Hi Bgooley - i am getting the same error message as above. Below is the error message

[#9]

My vm host system is UBUNTU 18.04, I did the following to fix the problem:

1. vi /etc/cloudera-scm-agent/config.ini

    server_host = (my master host's ip address)

2. run: getenforce, if the result is disabled, the go ahead, otherwise run: setenforce=0

3. disable firewalls

    systemctl stop  firewalld

    systemctl disable  firewalld

    systemctl ufw firewalld

    systemctl ufw firewalld 

4. check if networking service is running, if not, start it:

    systemctl start networking  (or run /etc/init.d/networking start)

Good luck!