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

Who agreed with this topic

Cloudera Installation Path B Fails -

Explorer
  • Parent Command: First Run ( )

Command Details: Deploy Client Configuration

Deploy Client Configuration - Failed to deploy client configuration

Execute command deployClientConfig on service HDFS - Failed 

Completed only 0/5 steps. First failure: Client configuration (id=1) on host <x.x.x.x> (id=4) exited with 1 and expected 0.

Execute command deployClientConfig on service Solr - Failed

Completed only 0/1 steps. First failure: Client configuration (id=2) on host<x.x.x.x> (id=1) exited with 1 and expected 0.

..... 

 

I applied the   cloudera-scm ALL=(ALL) NOPASSWD: using visudo on a Centos6.6 but still the installation fails,

usermod -a -G sudo cloudera-scm gave 

usermod: group 'sudo' does not exist

 

In the manager server log, I see

2016-04-05 11:26:40,518 ERROR main:org.hibernate.engine.jdbc.spi.SqlExceptionHelper: ORA-00942: table or view does not exist

 

In the manager agent log, I see

SError: [Errno 13] Permission denied: '/var/lib/zookeeper'
[05/Apr/2016 11:49:14 +0000] 4067 MainThread agent ERROR Could not evaluate resource {u'io': None, u'named_cpu': None, u'tcp_listen': None, u'dynamic': False, u'rlimits': None, u'file': None, u'memory': None, u'directory': {u'path': u'/var/lib/zookeeper', u'bytes_free_warning_threshhold_bytes': 0, u'group': u'cloudera-scm', u'user': u'cloudera-scm', u'mode': 493}, u'cpu': None}
Traceback (most recent call last):

 

In the Agent log, i see the following errors

Failed to connect to previous supervisor.

[05/Apr/2016 11:39:52 +0000] 4067 MainThread agent ERROR Failed to connect to previous supervisor.
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1529, in find_or_start_supervisor
self.configure_supervisor_clients()
File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1768, in configure_supervisor_clients

 

 

[05/Apr/2016 11:42:42 +0000] 4067 Monitor-HostMonitor throttling_logger ERROR Timeout with args ['/usr/java/jdk1.7.0_67-cloudera/bin/java', '-classpath', '/usr/share/cmf/lib/agent-5.4.7.jar', 'com.cloudera.cmon.agent.DnsTest']
None
[05/Apr/2016 11:42:44 +0000] 4067 Monitor-HostMonitor throttling_logger ERROR Failed to collect java-based DNS names
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/src/cmf/monitor/host/dns_names.py", line 64, in collect
result, stdout, stderr = self._subprocess_with_timeout(args, self._poll_timeout)

 

 

[05/Apr/2016 11:45:23 +0000] 4067 MainThread parcel ERROR Failed to activate alternatives for parcel CDH-5.4.7-1.cdh5.4.7.p0.3: 1
[05/Apr/2016 11:45:23 +0000] 4067 MainThread parcel INFO Executing command ['/usr/lib64/cmf/service/common/alternatives.sh', 'activate', 'solr-conf', '/etc/solr/conf', 'etc/solr/conf.dist', '10', 'True']
[05/Apr/2016 11:45:23 +0000] 4067 MainThread parcel ERROR Failed to activate alternatives for parcel CDH-5.4.7-1.cdh5.4.7.p0.3: 1
[05/Apr/2016 11:45:23 +0000] 4067 MainThread parcel INFO Executing command ['/usr/lib64/cmf/service/common/alternatives.sh', 'activate', 'hive-hcatalog-conf', '/etc/hive-hcatalog/conf', 'etc/hive-hcatalog/conf.dist', '10', 'True']

 

I am installing on AWS using the Centos 6.6 AMI ami-f35e56c3. is there anything else that needs to be done?

 

Who agreed with this topic