08-03-2017 06:10 AM - edited 08-03-2017 10:03 AM
Should have asked intially but totally forgot are you trying to configure multinode or single node ?
Kee the same ip as you like " 192.168.0.111 "
just type and see if the hostname is reflecting in your terminal like
Type echo $HOSTNAME in the terminal it should return as server1
Make sure your iptables / firewall is off in the machine that you are trying .
and fire the cloudera agent please let me know the update
08-03-2017 12:45 PM - edited 08-03-2017 12:51 PM
Thanks for the help.
I've tried installing in both single user and without. This is for a single node.
I tried that and it still appears to fail at the heartbeat. Quite frustrating
I turn off the firewall with : sudo ufw disable;
Also, adjust iptables with sudo iptables -A INPUT -p tcp --dport ssh -j ACCEPT;
08-03-2017 07:14 PM - edited 08-03-2017 07:30 PM
Bear with me mate . This issue comes when there is problem in the hostname configuration . Ideally your installer bin should prompt you like this http://server1:7180, if it prompt you like http:/localhost:7180 then it is a issue .
This has happened in previous cloudera manager version that is prior to CM 5.11.1 Checkout the below link
Search - ubuntu
I hope it is your test box so how be manipulate the host file and turn off the iptables
to see if that works.
Change this file to 127.0.0.1 localhost -- Remove it 127.0.1.1 gpu-serv1 --Remove it 192.168.0.67 server1
Turn off the iptables also.
I dont have a ubuntu box to help you I am out of station.
Sorry but last time you didnt tell if the $HOSTNAME returned your as server1 or not ?
do you mind give me a snapshot of your /etc/hostname and /etc/hosts file ?
08-04-2017 04:39 PM
Thanks again for your help.
That is what my /etc/hosts looks like now. I go to http://server1:7180 and try the wizard and it still fails at the heartbeat. When I scan to see, I can see that port 7182 is open and listening. I'm at a loss as to what I can do to fix this issue.
08-13-2017 09:36 AM - edited 08-13-2017 12:42 PM
Still having this persistent issue. Anyone have other thoughts?
I followed the instructions on most of the forums here when I searched for failed heartbeat, also http://www.yourtechchick.com/hadoop/failed-receive-heartbeat-agent-cloudera-hadoop/
When I run sudo iptables -L this is the result:
Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
and sudo ufw status verbose
sudo ufw status verbose
To recap, this is a single node installation, it will get through the install and stop at the failed hearbeat.