Replies: 5
Hello team; I failed to register the slaves using the ambari web interface.
The error against the failed nodes are (truncated for presentation):
STDOUT Cluster primary OS type is redhat6 and local OS type is centos6
STDERR Connection to 192.168.1.21 closed.
STDOUT sudo-1.8.6p3-7.el6.x86_64
STDERR Connection to 192.168.1.21 closed.
STDERR Connection to 192.168.1.21 closed.
STDERR Registering with the server…
Registration with the server failed.
Now I’m not sure if this is a psql error, as the below statement does not work
[root@master ~]# psql -U ambari-server -d ambari
psql: FATAL: no pg_hba.conf entry for host “[local]“, user “ambari-server”, database “ambari”, SSL off
But it seems more like a networking issue, and frankly I’m stumbling diagnosing networking errors. I might have a namespace issue for the slaves in relation with the master.
jekyll 192.168.1.68 (host os)
master 192.168.1.20 (guest vmware)
slave1 192.168.1.21 (guest vmware)
slave2 192.168.1.22 (guest vmware)
slave3 192.168.1.23 (guest vmware)
virtual networking: bridged
Also ambari-agents were successfully installed on the slaves using ambari-server:
[root@slave3 ~]# ambari-agent status
Found ambari-agent PID: 3426
ambari-agent running.
Agent PID at: /var/run/ambari-agent/ambari-agent.pid
Agent outout at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log
Does this provide any clues? Which, if any logs, would provide hints? I’m running out of ideas? Virtual network diagnosis is brutal. 