Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

amazon ec2 4 node cluster shows lost heart beat for all services and not able to start any services

avatar
New Member

amazon ec2 4 node cluster shows lost heart beat for all services and not able to start any services

1 ACCEPTED SOLUTION

avatar
New Member

invalid /etc/hosts file entry caused this.

View solution in original post

6 REPLIES 6

avatar
Master Mentor
@Anil Mathew

Not enough details provided like HDP version, Ambari version

ambari-agent restart in all the nodes and see if it helps.

avatar
New Member

node 1: ambari-server & ambari-agent

node 2: ambari-agent

node 3: ambari-agent

node 4: ambari-agent

restarted all agents, still in the ambari dashboard all hosts says heartbeat failure.

I'm using elastic ip with amazon ec2

avatar
New Member

HDP-2.3.2.0-2950

(2.3.2.0-2950

avatar
New Member

890-2015-12-16-22-03-29-ambari-hadoopcluster.jpg

Please see my host config screen.

also i updated the file /etc/ambari-agent/conf/ambari-agent.ini to point to ambari server

[server] hostname=52.33.91.17

url_port=8440

secured_url_port=8441

avatar
New Member

@Neeraj Sabharwal please check my above config screens and suggest help

avatar
New Member

invalid /etc/hosts file entry caused this.