search

davebond / vagrant-cloudera-multinode

Vagrant Cloudera setup with configurable number of nodes
3 stars 2 forks source link

Installation failed. Failed to receive heartbeat from agent #1

Open bradjcox opened 10 years ago

bradjcox commented 10 years ago

Install worked. Custom changes were to change all occurences of .cluster to .cox.dom as FQDN with these changes near the top:

Node settings

node_count = 3 node_ram = 2048

Everything went fine until Cloudera Manager's last step, which installed Java and CM agents on each slave then awaiting heartbeat from the agents. This failed with the message:

Installation failed. Failed to receive heartbeat from agent. Ensure that the host's hostname is configured properly. Ensure that port 7182 is accessible on the Cloudera Manager server (check firewall rules). Ensure that ports 9000 and 9001 are free on the host being added. Check agent logs in /var/log/cloudera-scm-agent/ on the host being added (some of the logs can be found in the installation details).

I've used CM before but am new to vagrant. Am unable to find whats wrong from this message. "Ensure hostname is correct (how? where? I thought vagrant would do this). "Ensure 7182 is accessable" (how? where? Why isn't vagrant handling this?). And so forth.

davebond commented 10 years ago

I'm getting the same issue, though all hosts can connect to each other with all ports open...

Though I can seem to get it to work by reloading the cluster.

vagrant reload

Then when it comes back up the hosts are available with an active heartbeat and you can continue the installation.

I'll take a better look when I get some free time.