Hello,   When adding a host, Cloudera Manager will execute a script on the host you are adding.  The script will attempt to install various packages.  For legacy support, the 1.6 JDK is installed even though you will not be using it.  When you see the error regarding the jdk install, you should be able to click on a link to get the details to understand why it failed.   If you chose to use the same repository as Cloudera Manager, the install should succeed, but it could be that on your new host there is another OS repository that contains the "jdk" package.  If that is the case, remove that repo configuration temporarily for the install.   At the least, if you can share with us the error that occurs to cause the failure, we can help further. ... View more

Hello,   If you see stderr output, then the supervisor.conf was already read.  The permissions error is not relevant, I think, as the supervisor runs as root and has permission to access.  The fact that you see stderr informaiton means the supervisor.conf was already read successfully and the process started as we see the "exec" line.   Check your NameNode log (usually in /var/log/hadoop-hdfs) for details about the failure.   From what you showed us, it appears the agent/supervisor started the NameNode but then it failed to stay running for more than a few seconds at most.   Let us know what you see in the log.     ... View more

Hi,   I wonder if you have the right agent package installed for your OS.   - What is your OS version? - What is the rpm -qa |grep cloudera output?   If you are on an OS that ships with python 2.7 natively, then the agent's virtual environment should also support that version.   Ben ... View more

Hello Karthi,   Thanks for bringing your questions to this community. I'll start by saying that the health issues you see stem from an inability for the Cloudera Manager agents on your host/hosts to communicate with Cloudera Manager on port 7182 and for your agent to communicate with the Host Monitor (to upload metrics) on port 9995.   It could be your agent is not started.  On your host or hosts, try running (as root or sudo):   service cloudera-scm-agent start   If you are lucky, that's all that needs to be done.  If the agents are running and you still see this problem, this gets into more complex troubleshooting.  In that case, I'd start by making sure that iptables is not restricting ports (turn it off on all hosts if it is on), try telneting or nc to the Cloudera Manager host's port 7182.   All that said, you may want to walk our quickstart tutorial here:   http://www.cloudera.com/developers/get-started-with-hadoop-tutorial.html   It might probe to be a good start since you are new to Cloudera and hadoop. We love that you are giving this a try so keep the questions coming.   NOTE:  for troubleshooting agent issues, your best friend is the agent log; by default it is:   /var/log/cloudera-scm-agent/cloudera-scm-agent.log   Look for python stack traces and error messages that could help you and us diagnose the issue. By default, the agent will try to heartbeat to the server that is configured in the "server_host" configuration in the agent's configurtation file ( /etc/cloudera-scm-agent/config.ini ).  So make sure that the host is that of your Cloudera Manager and it is resolvable on this host.   That's a lot, so I'll stop there.  Let us know if you get stuck.   Cheers,   Ben ... View more