Created 03-10-2016 01:57 AM
I am trying to add a new host to my existing cluster. Below is what I have done so far:
a.) I installed Ambari-Agent on the new hosts and modified the INI file to point to the ambari-server hosts
b.) Verified that new host is able to ping ambari-server and vice versa.
c.) Verified that the Ambari-Server port is open from the new hosts
What else Ambari-Server looks for ? If it can ping the new host and new host can ping and the ambari-server is reachable why it can't register. What's the missing part ?
Thanks
Prakash
Created 03-10-2016 04:02 AM
Ping is not enough. If you run iptables, stop them for a while to see if some ports are blocked. Agents are accessing the server at 8080, 8440 and 8441, and the server is pinging agents at 8670. Details are here. And, well, you haven't mentioned starting ambari-agent, but I'm sure you did it.
Created 01-16-2018 04:11 PM
I had a similar issue and wanted to add my findings to hopefully help those in the future reading this note. I went through all the above checks with ports, firewalls, TPH, etc and the new host still failed to register. Finally during some checking, I noticed the /etc/hosts file had a different name than what was in DNS for this host IP(the server was built with a different host name, then renamed without changing /etc/hosts). Since DNS resolved to the correct IP all the port checking worked. However, I assume when the ambari-agent was started it read the hosts file so it knew itself as the hostname in the /etc/hosts file which was incorrect. After updating the /etc/hosts file and restarting the ambari-agent everything worked.
Created 03-06-2018 05:23 AM
To solve this issues you should be known these things first:-
Created 04-21-2018 11:47 AM
So today I rebooted the machine and restarted Ambari-Agent and it was able to connect.. ince DNS resolved to the correct IP all the port checking worked. However, I assume when the ambari-agent
,Since DNS resolved to the correct IP all the port checking worked. However, I assume when the ambari-agent was started it read the hosts file so it knew itself as the hostname
Created 05-14-2018 01:40 PM
I want to Ambari to build a platform for testing some functionalities on spark. I use Win 10+Hyper-V to create two VMs (mercury.gc and venus.gc) installed with CentOS 7. Ambari 2.2.2.0 is installed on one VM (mercury.gc) and try to use it to config these two VMs.
Created 05-18-2018 01:26 PM
it is very nice blog<a href="http://julycalendar2018.com/">july2018 Calendar</a> <a href="http://julycalendar2018.com/">july 2018 Calendar printable</a> <a href="http://julycalendar2018.com/">july Calendar 2018 printable</a> <a href="http://julycalendar2018.com/">july 2018 Calendar template</a> <a href="http://julycalendar2018.com/">july 2018 blank Calendar</a> <a href="http://julycalendar2018.com/">2018 july Calendar</a> <a href="http://www.printcalendar2017.com/2018/04/july-2018-monthly-calendar-printable.html">2018 july Calendar</a> <a href="http://www.printcalendar2017.com/2018/04/july-2018-monthly-calendar-printable.html">calendar july 2018</a> <a href="http://www.printcalendar2017.com/2018/04/july-2018-monthly-calendar-printable.html">july 2018 Calendar</a> <a href="http://www.printcalendar2017.com/2018/05/free-july-2018-printable-calendar.html">free july 2018 template</a> <a href="http://www.printcalendar2017.com/2018/04/august-2018-monthly-calendar-printable.html">august 2018 Calendar</a> <a href="http://www.printcalendar2017.com/2018/04/august-2018-monthly-calendar-printable.html">august 2018 Calendar printable</a> <a href="http://www.printcalendar2017.com/2018/04/august-2018-monthly-calendar-printable.html">august Calendar 2018 printable</a> <a href="http://www.printcalendar2017.com/2018/04/august-2018-monthly-calendar-printable.html">august 2018 Calendar template</a> <a href="http://www.printcalendar2017.com/2018/04/august-2018-monthly-calendar-printable.html">august 2018 blank Calendar</a> <br>
Created 06-08-2018 05:45 PM
Created 07-02-2019 05:53 PM
Ambari agent could also fail due to a bug which requires:
force_https_protocol=PROTOCOL_TLSv1_2