Here is another question about getting hosts to register. I am using Ambari 1.7.0 on CentOS 6 machines. I am trying to install HDP 2.1.
First here is the hosts file I am using. Note each node has the same hosts file:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.200.144 datanode10.localdomain.com
192.168.200.107 datanode01.localdomain.com
192.168.200.143 namenode.localdomain.com
Also, I can ping each machine for any machine.
I can SSH without a password from the name node into the other datanodes.
I disabled selinux and iptables on all machines.
I am following the startup procedure listed here: https://cwiki.apache.org/confluence/display/AMBARI/Install+Ambari+1.7.0+from+Public+Repositories. Please note that these install instructions mention nothing about iptables or selinux. People on the mailing list have told me that I need to disable those items.
Ambari can discover the namenode it is sitting on. It cannot discover the datanodes. I get this error from the registration log file:
—
==========================
Running setup agent script…
==========================
…
Verifying ambari-agent process status…
Ambari Agent successfully started
Agent PID at: /var/run/ambari-agent/ambari-agent.pid
Agent out at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log
(“WARNING 2014-12-17 10:43:08,349 NetUtil.py:92 – Server at https://namenode.localdomain.com.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode.namenode:8440 is not reachable, sleeping for 10 seconds…
—
Why is the namenode being appended to the namenode.localdomain.com URL? Why is the script considering this a valid
URL and not throwing an error?