Member since
08-08-2013
339
Posts
132
Kudos Received
27
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
14836 | 01-18-2018 08:38 AM | |
1578 | 05-11-2017 06:50 PM | |
9197 | 04-28-2017 11:00 AM | |
3444 | 04-12-2017 01:36 AM | |
2846 | 02-14-2017 05:11 AM |
11-14-2017
06:08 AM
A few days ago, I happened to run into this issue myself. The root cause is, when installing Ranger, in the "External URL" property, the administrator entered "http://hostname.example.com:6080/", instead of the expected "http://hostname.example.com:6080" (WITHOUT the trailing slash character). Even though the Ranger installation would go through, Ranger's Usersync would log errors in /var/log/ranger/usersync/usersync.log due to this extraneous character. Also, any attempt to enable any of Ranger's plugins would fail, with the error message "Ambari admin username and password are blank", because Ranger is indeed missing many users, including the important one amb_ranger_admin. To fix this, just edit this property and remove any character after port 6080, and everything will start working.
... View more
04-21-2016
07:55 AM
That's fine, thanks Artem.
... View more
04-18-2016
02:45 PM
Brilliant @Predrag Minovic , that solved the issue. Thanks !
... View more
03-26-2016
10:34 AM
Hi @Jonas Straub , Hi @Ramesh Mani , I just wanted to update with the solution of that issue. At the end it turned out, that after Ambari upgrade (from 2.0.1 initially to Ambari 2.1.2.1), the placeholder-variables were not set/applied correctly via Ambari. In HDFS => advanced ranger-plugin config there were variables like {{xaaudit_db_XYZ}}, and I replaced those with their real values (xaaudit.db.username, xaaudit.db.database, xaaudit.db.password, ...) , restarted HDFS and now the audit log entries are being written. Regards, Gerd
... View more
03-21-2016
02:04 PM
Hi @Artem Ervits , if I will find the time to do so, I'll post an article here, for sure 😉
... View more
03-12-2016
01:05 PM
2 Kudos
Hello @Ancil McBarnett , I checked that ranger-admin-site.xml, it was not updated there. I was wondering, since I am using HDP2.2.4, why is that file under .../HDP/2.3/... ?!?! Anyways, I set the port to 6182, but unfortunately after restarting Ranger the alert was still there. So I searched for other RANGER configs, because of the HDP2.2.4 vs. HDP2.3 and at the end it turned out that I had to update the port in file /var/lib/ambari-server/resources/common-services/RANGER/0.4.0/configuration/ranger-site.xml After restarting Ranger the alert disappeared. Many thanks for this hint...
... View more
03-07-2016
10:05 AM
2 Kudos
To disable SSLv3 for old Hue version, do the following: 1.) open file "/usr/lib/hue/desktop/core/src/desktop/lib/wsgiserver.py" 2.) add the following line, after line no. 1669: ctx.set_options(SSL.OP_NO_SSLv2 | SSL.OP_NO_SSLv3) 3.) restart Hue To check if Hue replies on SSLv3 or not you can use this one: openssl s_client -connect <hue-server-name>:<hue-port> -ssl3 Here the corresponding GitHub patch, thanks to @cdraper: https://github.com/cloudera/hue/commit/0060abf9aae0049c082c9948658eea7df848ab6e
... View more
Labels:
03-07-2016
09:25 AM
Solution found, and published here: https://community.hortonworks.com/articles/21650/disable-sslv3-for-hue-v261.html
... View more
12-22-2017
06:45 PM
@ Ryan Chaplin/@Mark Petronic I am unable to connect on hive through knox using zokeeper dynamic discovery. Below details of my cluster. HDP: 2.6 Kerberos Enabled: YES ( Windows AD 2012 R2) Authentication: AD with LDAPS ( Windows AD 2012 R2) Ranger Enabled: YES RANGER Usersync and GroupSync: YES with windows AD Ambari Enabled AD: YES KNOX Enabled with AD: YES (except Admin account/topology) KNOX advance topology have definition for zookeeper dynamic discovery and webhdfs ha: YES While connecting on HIVE through beeline getting error as "Invalid status 72 (state=08S01,code=0)" [ajay@vijayhdp-1 ~]$ beeline Beeline version 1.2.1000.2.6.3.0-235 by Apache Hive beeline> !connect jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive Connecting to jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive Enter username for jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive: ajay Enter password for jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive: ******** 17/12/22 15:43:57 [main]: WARN jdbc.HiveConnection: Failed to connect to vijayhdp-1.novalocal:8443 Error: Could not open client transport with JDBC Uri: jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive: Invalid status 72 (state=08S01,code=0) 0: jdbc:hive2://vijayhdp-1.novalocal:8443/ (closed)> Kindly suggest to fix it. - Vijay Mishra , @Ryan Chapin I am unable to connect on hive through knox using zokeeper dynamic discovery. Below details of my cluster. HDP: 2.6 Kerberos Enabled: YES ( Windows AD 2012 R2) Authentication: AD with LDAPS ( Windows AD 2012 R2) Ranger Enabled: YES RANGER Usersync and GroupSync: YES with windows AD Ambari Enabled AD: YES KNOX Enabled with AD: YES (except Admin account/topology) KNOX advance topology have definition for zookeeper dynamic discovery and webhdfs ha: YES While connecting on HIVE through beeline getting error as "Invalid status 72 (state=08S01,code=0)" [ajay@vijayhdp-1 ~]$ beeline
Beeline version 1.2.1000.2.6.3.0-235 by Apache Hive
beeline> !connect jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive
Connecting to jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive
Enter username for jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive: ajay
Enter password for jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive: ********
17/12/22 15:43:57 [main]: WARN jdbc.HiveConnection: Failed to connect to vijayhdp-1.novalocal:8443
Error: Could not open client transport with JDBC Uri: jdbc:hive2://vijayhdp-1.novalocal:8443/;ssl=true;sslTrustStore=/tmp/myLocalTrustStore.jks;trustStorePassword=password?transportMode=http;httpPath=gateway/default/hive: Invalid status 72 (state=08S01,code=0)
0: jdbc:hive2://vijayhdp-1.novalocal:8443/ (closed)> Kindly suggest to fix it. - Vijay Mishra
... View more