- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
amazon ec2 4 node cluster shows lost heart beat for all services and not able to start any services
Created ‎12-17-2015 03:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
amazon ec2 4 node cluster shows lost heart beat for all services and not able to start any services
Created ‎12-17-2015 05:05 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
invalid /etc/hosts file entry caused this.
Created ‎12-17-2015 03:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not enough details provided like HDP version, Ambari version
ambari-agent restart in all the nodes and see if it helps.
Created ‎12-17-2015 04:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎12-17-2015 04:01 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HDP-2.3.2.0-2950
(2.3.2.0-2950
Created on ‎12-17-2015 04:06 AM - edited ‎08-19-2019 05:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎12-17-2015 04:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Neeraj Sabharwal please check my above config screens and suggest help
Created ‎12-17-2015 05:05 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
invalid /etc/hosts file entry caused this.
