Support Questions
Find answers, ask questions, and share your expertise
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

CDH 5.3.2 installation failure

CDH 5.3.2 installation failure




I use a 4 node cluster to install Cloudera 5.3.2. The servers are RHEL 6.5. The installation fails on the three data nodes and the error is


scm agent is already configured
Starting Cloudera Manager Agent...
BEGIN /sbin/service cloudera-scm-agent status | grep running
END (1)
BEGIN /sbin/service cloudera-scm-agent start
/etc/init.d/cloudera-scm-agent: line 123: /var/log/cloudera-scm-agent/cloudera-scm-agent.out: No such file or directory
Starting cloudera-scm-agent: /etc/init.d/cloudera-scm-agent: line 126: /var/log/cloudera-scm-agent/cloudera-scm-agent.out: No such file or directory
END (1)
agent logs:
BEGIN tail -n 50 /var/log/cloudera-scm-agent//cloudera-scm-agent.out | sed 's/^/>>/'
tail: cannot open `/var/log/cloudera-scm-agent//cloudera-scm-agent.out' for reading: No such file or directory
tail: cannot open `/var/log/cloudera-scm-agent//cloudera-scm-agent.out' for reading: No such file or directory
END (0)


In the installed node the logs are 


Installing cloudera-manager-agent package...
BEGIN yum list installed cloudera-manager-agent
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Error: No matching Packages to list
END (1)


Please help to resolve this.





Re: CDH 5.3.2 installation failure

Expert Contributor



Just a few checks


1. Do you have a proxy?  

2. Did you setup the proxy?

3. Also setup environment? /etc/environment

4. Did you ssh-copy-id to each machine and test each machine to each other?

5. Have you updated yum with cloudera repo?

6. You run update to make sure yum update is working?


Have you tried manually trying to install the agent just for a test to see if it works?


Just sounds like you don't have yum setup correctly or the environment.