Member since
01-15-2015
313
Posts
28
Kudos Received
25
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1058 | 10-19-2021 12:04 AM | |
4289 | 10-18-2021 11:54 PM | |
1583 | 05-04-2021 02:38 AM | |
6012 | 11-19-2020 05:48 AM | |
6044 | 11-18-2020 12:08 AM |
10-09-2019
12:25 AM
There are no plans to add support to C5 releases. See currently supported OS versions
... View more
09-04-2019
01:28 PM
Is there a reason you can share, or a link to something that explains why disabling SELinux is necessary, and why we can't have nice things?
... View more
05-15-2019
10:50 PM
I have changed this line in my.cnf: socket=/var/lib/mysql/mysql.sock to this socket=/var/run/mysqld/mysql.sock and that fixed it! I think Cloudera has to review its installation guide ... I have faced many difficulties so far ... They tell you to do A and B to get C ... you do A and B but you don't get C!! ...
... View more
05-15-2019
01:24 AM
This confirmes the package is installed correctly, and the JDK is installed to /usr/lib/jvm/java-8-oracle-cloudera/ You may want to use this as JAVA_HOME when configuring CM and the cluster to use this JDK
... View more
05-10-2019
12:32 AM
@JoaquinS Your CM agent config file does not have TLS enabled, but the CM server configuration has. I would suggest to disable the Use TLS Encryption for Agents, Use TLS Authentication of Agents to Server, Verify Agent Hostname Against Certificate settings and restart CM to proceed to make the installation work in a first step. Once that is done, please follow the steps in this documentation chapter to enable TLS encryption for CM agent communication.
... View more
05-03-2019
04:29 PM
Thank you gzigldrum Ill follow the same below.Appreciate your time here! Regards Yasmeen
... View more
04-08-2019
09:05 AM
Thanks, @gzigldrum , for the explanation!
... View more
04-05-2019
05:55 AM
Please attempt to start CM server again @sbommaraju Then look up /var/log/cloudera-scm-server/cloudera-scm-server.log as this should indicate potential reason for the startup failure. Also we suggest to start your own thread in the forums if you need further help with this startup error
... View more
04-03-2019
11:37 PM
Hi Gzigldrum, Thank you for the reply, I found the Route cause and resolved the issue myself, my proxy server principal is not listing in the impla demon keytab , impla/proxy@relim in none of the demon nodes, i cross checked the Impala Daemons Load Balancer has confiured to Executor group feild eariler with value " proxyhost:port" this where its not reflecting ,because none of the impla demon nodes are present in executor group . All the impla demon nodes are present in "impala demon default group, i have added the value '"proxyhost:port" in this field and restarted the impala service, when is cross cehck the princaipl in demon node the impala keytab has the impla/proxy@relim, and the kerberos authentication from proxy server started working fro the impala. Regards, Pandu
... View more