Member since
01-11-2016
36
Posts
3
Kudos Received
6
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3817 | 04-26-2017 05:31 PM | |
3294 | 02-14-2017 06:57 PM | |
6632 | 01-26-2017 02:47 PM | |
4295 | 04-21-2016 04:26 PM | |
2633 | 04-18-2016 11:11 PM |
02-06-2023
05:52 AM
Hello ozzielabrat, I am also facing same issue, what is the solution for it. Thanks
... View more
04-26-2017
05:31 PM
Thanks Romain ! I forgot to mention, we are using CDH 5.7.1 and I originally setup the Hue database to be a MySQL external DB (migrated from embedded). This morning (only about 30 minutes ago) I restored the Hue MySQL database from a backup (before the Oozie Workflows were deleted), and at this stage all the Hue Control Nodes and DAG components for each WF look like they are fine. Our Oozie Workflow Guru (my collegue who wrote all the WF's) is now looking through them in Hue to confirm they all look and work OK. Thankyou so much for your quick response. Cheers, Damion.
... View more
02-17-2017
12:23 AM
1 Kudo
Kerberos and LDAP for Impala are different. MS AD provide both but configuring Hadoop and Impala for Kerberos uses that for auth and not LDAP. Based on what you said and the message from using the base command I'd say you are using Kerberos. Below is the command you need to use. impala-shell -k -i FQDN --ssl
... View more
02-14-2017
06:57 PM
1 Kudo
We have resolved this issue. Turns out it was a compatibility issue in our wonderfull Internet Explorer browser.
... View more
01-26-2017
02:47 PM
Problem resolved....a case of PEBCAK.... I needed to generate the Kerberos user/principal keytab file using the "ktutil" command before trying to "kinit" using the keytab: kinit dreeves@{obfuscated-realm}.COM.AU -k -t dreeves.keytab Once that was completed, "hdfs dfs -ls /" worked without a problem.
... View more
04-22-2016
07:55 AM
Hello, Great, good to read it! Cheers, Peter
... View more
04-19-2016
05:19 AM
It happens to everyone. Thanks for sharing the solution. 🙂
... View more
03-24-2016
08:36 AM
When you say you're having the same issue, I need some clarification. The original poster was complaining that Director could not make an HTTP connection to Cloudera Manager on port 7180. You seem to be saying that Director (and you yourself) cannot establish an SSH connection to an instance (on port 22). These are likely two different problems. If this is correct, can you please open a separate question, and post a snippet from Director's application.log showing the failure to establish a connection? That way future forum users can benefit from whatever solution we find.
... View more
01-31-2016
01:37 PM
Thankyou for the quick update Vinithra, much appreciated. Regards, Damion.
... View more