Member since
02-23-2018
14
Posts
5
Kudos Received
0
Solutions
06-20-2018
09:27 AM
Hi, Here are some details with Ranger logs (a part of it) : Usersync log : INFO PasswordValidator [Thread-64968] - Response [FAILED: [amb_ranger_admin] does not exists.] for user: amb_ranger_admin INFO PasswordValidator [Thread-64970] - Response [FAILED: [admin] does not exists.] for user: admin >>> Those are infos to say these users are not UNIX users. That's all the logs we have (hundred times a day). For me, it is not our main problem. XAPORTAL log : 2018-06-20 09:10:29,691 [http-bio-6080-exec-8] INFO org.apache.ranger.security.handler.RangerAuthenticationProvider (RangerAuthenticationProvider.java:147) - Authentication with SHA-256 failed. Now trying with MD5. 2018-06-20 09:10:29,692 [http-bio-6080-exec-8] INFO org.apache.ranger.security.listener.SpringEventListener (SpringEventListener.java:70) - Login Successful:admin | Ip Address:128.1.227.103 | sessionId=A311983F0813A5EDE4B4F34FDF558628 | Epoch=1529485829692 2018-06-20 09:10:29,698 [http-bio-6080-exec-8] INFO org.apache.ranger.biz.SessionMgr (SessionMgr.java:232) - UserSession Updated to set new Permissions to User: admin 2018-06-20 09:10:29,698 [http-bio-6080-exec-8] INFO org.apache.ranger.biz.SessionMgr (SessionMgr.java:184) - Login Success: loginId=admin, sessionId=51435, sessionId=A311983F0813A5EDE4B4F34FDF558628, requestId=128.1.227.103, epoch=1529485829698 >>> No Warning or Error CATALINA.OUT log : RemoteUnixLoginModule: RemoteUnixLoginModule::initialize() has been called with callbackhandler: org.springframework.security.authentication.jaas.AbstractJaasAuthenticationProvider$InternalCallbackHandler@12a420aa RemoteUnixLoginModule: Created RemoteUnixLoginModule >>> All good Access_log is good aswell. We don't see errors, in any Ranger log. Do you have some tips for HDFS/Ranger configuration check ? Thanks, Tom
... View more
06-15-2018
02:36 PM
@Felix Albani yes it is. All seems good in Ranger Admin view. You add this in the Custom hdfs-log4j ? The parameter isn't here yet for us in log4j conf.
... View more
06-15-2018
01:39 PM
@Felix Albani Here you got the screen, no apparent problem : That's why we think it's about some HDFS or Ranger parameters, all seems good in the Admin console.
... View more
06-15-2018
01:12 PM
Hi @Felix Albani Thank for your answer. We already intended the slash and wildcard /* without success unfortunately. We waited a few minutes to let Ranger some time to apply its rules : it didn't change anything. It really seems that Ranger can't overwrite the HDFS 700 (rwx------) permissions we set before. We are now working with a specific folder and it's the same problem, but the policy is well configured too : We are now looking for some parameters in Ranger / HDFS to try and check because Ranger Admin seems to be correctly configured. Tom C
... View more
06-15-2018
10:00 AM
1 Kudo
Hi all, We are trying to add Ranger in our cluster to secure users access. After the installation, we configured policies in Ranger with the rights we wanted (see the picture below for the most permissive policy). Then, we made a CHMOD -R 700 on test folder to verify Ranger's policy effect. But it seems that Ranger policies are not considered. Typical error we get with the file view : org.apache.hadoop.security.AccessControlException: Permission denied: user=test, access=READ_EXECUTE, inode="/tmp/RangerTestFolder":admin:hdfs:drwx------
Ranger is well configured and Test Connection is "Connected Successfully" for HDFS. We followed these instructions (+ some forums) : https://fr.hortonworks.com/blog/best-practices-in-hdfs-authorization-with-apache-ranger/ But the problem is still remaining and we don't know why. How can we make RANGER permissions more important than HDFS ones ? Because it seems to be the case. Thanks, Tom
... View more
Labels:
- Labels:
-
Apache Hadoop
-
Apache Ranger
03-02-2018
03:53 PM
Hi @Manfred PAUL You are right and we are are currently in Ambari configuration. As the Ambari database was dropped, there is nothing left when you add the hosts. But we can use XML files on the host to find most of the parameters, they have not been deleted. We re-installed first, now we are looking for our past specific parameters. This is why backup is important !
... View more
02-28-2018
01:13 PM
1 Kudo
Here are some news @Jordan Moore @Timothy Spann : Adding existing hosts with a new Ambari-Server worked well ! We got all the HDFS data back. We added the same roles present before the crash, configured PGSQL for Hive and Oozie. We got some missing blocks in /ats/done/... due to the stop/start of HDFS services but it's not critical and it's only 74 / 570.000 blocks. We are now working on Ambari configuration and Hive Metastore. And of course, backups are coming ! Thanks for your help.
... View more
02-26-2018
09:09 AM
Hello, With which user did you install your Ambari-Server during the ambari-server setup ? Default is root. It looks like permission issue to me. If you don't remember the user, check Ambari-Server logs on /var/log/ambari-server/ambari-server.log. When you found it, run chown -R <AMBARI-USER> /var/run/ambari-server Tell us if it works better after. Thomas
... View more
02-24-2018
09:22 PM
1 Kudo
@Timothy Spann Yes, it's planned ! Jordan's solution seems interesting to you ?
... View more
02-24-2018
08:02 PM
@Jordan Moore Thanks again for the advice. We will try this solution to rebuild a new Ambari-Server without data loss. For the Hive Metastore, the problem is the same as Ambari-Server : the database is corrupted (there were Ambari, Hive, Hue and Oozie databases on the impacted host). We will have to build a new one i guess.
... View more