Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Registration with the server failed Ambari EC2

Registration with the server failed Ambari EC2

Hi i'm new to Hortonworks and Amazon EC2, and i'm trying to create my cluster with ambari, the node where ambari is installed works fine but the other nodes fails with this message

Command start time 2016-09-18 12:41:17
('INFO 2016-09-18 12:41:18,404 main.py:74 - loglevel=logging.INFO
WARNING 2016-09-18 12:41:18,409 NetUtil.py:82 - Failed to connect to https://ip-172-31-26-XXX.XXX.XXX.internal:8440/ca due to [Errno 4] Interrupted system call  
WARNING 2016-09-18 12:41:18,409 NetUtil.py:105 - Server at https://ip-172-31-26-XXX.XXX.XXX.internal:8440 is not reachable, sleeping for 10 seconds...
ERROR 2016-09-18 12:41:23,418 main.py:315 - Fatal exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 312, in <module>
    main(heartbeat_stop_callback)
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 248, in main
    stop_agent()
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 198, in stop_agent
    sys.exit(1)
SystemExit: 1
INFO 2016-09-18 12:41:23,418 ExitHelper.py:53 - Performing cleanup before exiting...
INFO 2016-09-18 12:41:23,663 main.py:74 - loglevel=logging.INFO
INFO 2016-09-18 12:41:23,665 DataCleaner.py:39 - Data cleanup thread started
INFO 2016-09-18 12:41:23,666 DataCleaner.py:120 - Data cleanup started
INFO 2016-09-18 12:41:23,666 DataCleaner.py:122 - Data cleanup finished
INFO 2016-09-18 12:41:23,679 PingPortListener.py:50 - Ping port listener started on port: 8670
INFO 2016-09-18 12:41:23,680 main.py:289 - Connecting to Ambari server at https://ip-172-31-26-XXX.XXX.XXX.internal:8440 (172.31.26.XXX)
INFO 2016-09-18 12:41:23,680 NetUtil.py:59 - Connecting to https://ip-172-31-26-XXX.XXX.XXX.internal:8440/ca
', None)
('INFO 2016-09-18 12:41:18,404 main.py:74 - loglevel=logging.INFO
WARNING 2016-09-18 12:41:18,409 NetUtil.py:82 - Failed to connect to https://ip-172-31-26-XXX.XXX.XXX.internal:8440/ca due to [Errno 4] Interrupted system call  
WARNING 2016-09-18 12:41:18,409 NetUtil.py:105 - Server at https://ip-172-31-26-XXX.XXX.XXX.internal:8440 is not reachable, sleeping for 10 seconds...
ERROR 2016-09-18 12:41:23,418 main.py:315 - Fatal exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 312, in <module>
    main(heartbeat_stop_callback)
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 248, in main
    stop_agent()
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 198, in stop_agent
    sys.exit(1)
SystemExit: 1
INFO 2016-09-18 12:41:23,418 ExitHelper.py:53 - Performing cleanup before exiting...
INFO 2016-09-18 12:41:23,663 main.py:74 - loglevel=logging.INFO
INFO 2016-09-18 12:41:23,665 DataCleaner.py:39 - Data cleanup thread started
INFO 2016-09-18 12:41:23,666 DataCleaner.py:120 - Data cleanup started
INFO 2016-09-18 12:41:23,666 DataCleaner.py:122 - Data cleanup finished
INFO 2016-09-18 12:41:23,679 PingPortListener.py:50 - Ping port listener started on port: 8670
INFO 2016-09-18 12:41:23,680 main.py:289 - Connecting to Ambari server at https://ip-172-31-26-XXX.XXX.XXX.internal:8440 (172.31.26.XXX)
INFO 2016-09-18 12:41:23,680 NetUtil.py:59 - Connecting to https://ip-172-31-26-XXX.XXX.XXX.internal:8440/ca
', None)
Connection to ip-172-31-16-121.XXX.XXX.internal closed.
SSH command execution finished
host=ip-172-31-16-121.XXX.XXX.internal, exitcode=0
Command end time 2016-09-18 12:41:26
Registering with the server...

Any idea why it fails ?

2 REPLIES 2
Highlighted

Re: Registration with the server failed Ambari EC2

@nedox nedox Were you able to resolve this issue?

Highlighted

Re: Registration with the server failed Ambari EC2

Guru

@nedox nedox @Saisubramaniam Gopalakrishnan

I've seen something similar once when the ports were not open an blocking the internal communication from the Ambari node to the other nodes in the cluster. It might be worth trying to open up the internal IP traffic and trying again to see if it resolves the issue, and then harden as needed afterwards.

Don't have an account?
Coming from Hortonworks? Activate your account here