Reply
New Contributor
Posts: 10
Registered: ‎08-09-2017

Re: Cloudera Manager. Agent cannot connect with supervisor. Failed to receive heartbeat from agent

[root@bigdata-master cloudera-scm-agent]# cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Tue Aug 8 03:48:20 2017
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=6a383e2f-6ebf-4654-b3ef-cd7917564a78 / xfs defaults 0 0
UUID=b347299f-6786-4f12-a3eb-84d580423ebc /boot xfs defaults 0 0
UUID=6523647e-3167-4caf-a3cc-135dc081b1b8 swap swap defaults 0 0

 

this is my fstab file content,i am not sure where the problem is.

Champion
Posts: 680
Registered: ‎05-16-2016

Re: Cloudera Manager. Agent cannot connect with supervisor. Failed to receive heartbeat from agent

could you share your /etc/hosts ? 

status of your firewall ? 

what os are you runining  ? 

 

New Contributor
Posts: 10
Registered: ‎08-09-2017

Re: Cloudera Manager. Agent cannot connect with supervisor. Failed to receive heartbeat from agent

thus,i have post a new topic at https://community.cloudera.com/t5/Cloudera-Manager-Installation/CDH-5-12-0-clouder-manager-agent-can... infomation is post on this url.thks for help.

New Contributor
Posts: 2
Registered: ‎04-11-2018

Re: Cloudera Manager. Agent cannot connect with supervisor. Failed to receive heartbeat from agent

To resolve this issue you need to check first all port opened on your server service listing to the port no, use command - sudo netstat -lpten check if any thing is running on 9000 or 90001, mostly java services required for set up is running on port 9000, and cloudera-scm-agent listner also runs on port 9000. to over come this issue you can re-configure theports as well in /etc/cloudera-scm-agent/config.ini by changing as below:-

 

# Hostname of the CM server.
server_host=10.34.156.118

# Port that the CM server is listening on.
server_port=7182

## It should not normally be necessary to modify these.
# Port that the CM agent should listen on.
listening_port=9001

 

It should not normally be necessary to modify these. # Port that the CM agent should listen on 9001

and then restart the cloudera-scm-agent service by command:- $ service cloudera-scm-agent restart TO verify this port is not activated for other sshd service check Ports opened in /etc/ssh/sshd_config.

 

I hope this resolution will work for others too.

Cheers,

Ankit Gupta

Announcements