Unable to register ambari hosts

[#1]

I'm using ambari 2.5 with Centos 7. Im unable to register agents with server. Below is the error.

INFO 2017-07-19 07:08:38,620 ExitHelper.py:56 - Performing cleanup before exiting... INFO 2017-07-19 07:08:50,315 main.py:145 - loglevel=logging.INFO INFO

2017-07-19 07:08:50,315 main.py:145 - loglevel=logging.INFO INFO 2017-07-19 07:08:50,315 main.py:145 - loglevel=logging.INFO INFO

2017-07-19 07:08:50,317 DataCleaner.py:39 - Data cleanup thread started INFO 2017-07-19 07:08:50,318 DataCleaner.py:120 - Data cleanup started INFO

2017-07-19 07:08:50,318 DataCleaner.py:122 - Data cleanup finished INFO 2017-07-19 07:08:50,322 PingPortListener.py:50 - Ping port listener started on port: 8670 INFO

2017-07-19 07:08:50,323 main.py:437 - Connecting to Ambari server at https://ip-172-31-27-38.ap-south-1.compute.internal:8440 (172.31.27.38) INFO

2017-07-19 07:08:50,323 NetUtil.py:70 - Connecting to https://ip-172-31-27-38.ap-south-1.compute.internal:8440/ca WARNING 2017-07-19 07:10:57,538 NetUtil.py:101 - Failed to connect to https://ip-172-31-27-38.ap-south-1.compute.internal:8440/ca due to [Errno 110] Connection timed out WARNING

2017-07-19 07:10:57,539 NetUtil.py:124 - Server at https://ip-172-31-27-38.ap-south-1.compute.internal:8440 is not reachable, sleeping for 10 seconds... INFO

2017-07-19 07:11:07,539 NetUtil.py:70 - Connecting to https://ip-172-31-27-38.ap-south-1.compute.internal:8440/ca

[#2 · Accepted solution]

@Rajesh Reddy

Are you sure that your Ambari Server FQDN is "ip-172-31-27-38.ap-south-1.compute.internal"

Is this FQDN accessible from the Agent machines? (I means from the agent machines are you able to resolve this hostname ?)

ping ip-172-31-27-38.ap-south-1.compute.internal

- Are you able to access the port 8440 from agent machine? (this is to isolate any N/W or Firewall issue)

# telnet   ip-172-31-27-38.ap-south-1.compute.internal   8440

.

- If above command does not connect to the ambari server on port 8440 then please check the IPTables on the ambari server if the firewall is disabled or not?

# service iptables stop

.

[#3]

My bad the issue was 8440 was not allowed in my AWS Security Groups.

[#4]

Hi, I have the same problem, where I can change port 8440, to another.