Created on 07-18-2017 07:51 AM - edited 07-18-2017 08:00 AM
You need to chang the /etc/sysconfig/network file each node accordinly for example
Node 1
/etc/sysconfig/network on node 1 NETWORKING=yes HOSTNAME=node1 NETWORKING_IPV6=no
Restart the network and you should be able to fix the error
Let me know if that helps
Created 07-18-2017 07:57 AM
Hello CSGUNA !
Thanks for help, but what do you recommend for ubuntu 14 ?
Created 07-18-2017 08:11 AM
I dont have the ubuntu on my test machine but I am na tell you anyways
do the same in Ubuntu
/etc/hosts
192.168.200.11 Master
In the Master node
The /etc/hostname file should contain
Master
Created 07-18-2017 05:37 PM
@darkdante were you able to receive heartbeat from agent.
Created 07-18-2017 05:59 PM
Hi csguna,
Here's the cloudera-scm-agent.log
[18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO To override these variables, use /etc/cloudera-scm-agent/config.ini. Environment variables for CDH locations are not used when CDH is installed from parcels. [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Created /run/cloudera-scm-agent/process [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Chmod'ing /run/cloudera-scm-agent/process to 0751 [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Created /run/cloudera-scm-agent/supervisor [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Chmod'ing /run/cloudera-scm-agent/supervisor to 0751 [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Created /run/cloudera-scm-agent/flood [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Chowning /run/cloudera-scm-agent/flood to cloudera-scm (988) cloudera-scm (983) [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Chmod'ing /run/cloudera-scm-agent/flood to 0751 [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Created /run/cloudera-scm-agent/supervisor/include [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent INFO Chmod'ing /run/cloudera-scm-agent/supervisor/include to 0751 [18/Jul/2017 17:38:20 +0000] 15294 MainThread agent ERROR Failed to connect to previous supervisor. Traceback (most recent call last): File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2109, in find_or_start_supervisor self.configure_supervisor_clients() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2290, in configure_supervisor_clients supervisor_options.realize(args=["-c", os.path.join(self.supervisor_dir, "supervisord.conf")]) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 1599, in realize Options.realize(self, *arg, **kw) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 333, in realize self.process_config() File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 341, in process_config self.process_config_file(do_usage) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 376, in process_config_file self.usage(str(msg)) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 164, in usage self.exit(2) SystemExit: 2 [18/Jul/2017 17:38:21 +0000] 15294 Dummy-1 daemonize WARNING Stopping daemon. [18/Jul/2017 17:38:21 +0000] 15294 Dummy-1 agent INFO Stopping agent... [18/Jul/2017 17:38:21 +0000] 15294 Dummy-1 agent INFO No extant cgroups; unmounting any cgroup roots
and this is the result of ps aux | grep supervisor
root 15823 0.0 0.0 112644 972 pts/1 S+ 17:57 0:00 grep --color=auto supervisor
As of today, it still outputs heartbeat failure.
Created 07-18-2017 06:35 PM
bear with me but did you change the /etc/sysconfig/network file in all the nodes 1 2 3 4 as mentioned earlier ?
did you restart the network in your os ?
Created 07-24-2017 07:08 AM
At the end what worked for me was:
1) kernel update to the newest version
2) removal of all the alternatives to java and javac, e.g. https://askubuntu.com/questions/613016/removing-oracle-jdk-and-re-configuring-update-alternatives
Created 07-24-2017 08:20 AM
This is what I did instead. I followed Path B and downloaded 5.11.1 version instead. Solved all of my problems.
Created 08-16-2017 12:35 AM
I still have the same problem with slight modifications :)
I was able to roll back the agent to 5.11, but the rest of cluster were successfully upgrated to 5.12.
So, the 5.11 agent works fine, but the node is not visible on the Cloudera Manager 5.12.
Created on 11-01-2017 11:07 AM - edited 11-01-2017 11:10 AM
Using 5.11 instead of 5.13 did not work for me. Neither did work the change in /etc/sysconfig/network:
NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=poweredge