Member since
09-08-2022
7
Posts
3
Kudos Received
0
Solutions
06-18-2024
01:22 AM
1 Kudo
To troubleshoot the issue of ranger policies not getting synced, you can check the following log files in HDFS: 1. ranger_admin.log: This log file contains the logs related to the Ranger Admin service. It can be found in the Ranger Admin node at the location: `/var/log/ranger/ranger-admin`. 2. ranger_admin_audit.log: This log file contains the logs for auditing actions performed by Ranger Admin. It can be found at the same location as ranger_admin.log.= 3. hdfs.log: This log file contains the logs for HDFS operations. It can be found in the Hadoop log folder, which is usually located at: `/var/log/hadoop/hdfs` or `/var/log/hadoop-hdfs`
... View more
03-20-2024
10:54 PM
1 Kudo
Hi @josr89 you can provide WRITE access to user "userA" to the below path under the "cm_hdfs" repository in Ranger, wait for plugins to sync and then rerun the operation. path: /apps/hbase/data/staging
... View more
08-01-2023
12:13 AM
1 Kudo
Hi @Kartik_Agarwal ! I solved this a couple of weeks ago, but you are right with your comments: In my case the file was having the right permission set, but the parent directory had not. So with the change of permissions to the parent directory, it worked fine. Thanks for your support!
... View more
03-10-2023
07:17 AM
1 Kudo
Hello @josr89 Thanks for using Cloudera Community. You have mentioned Hadoop 3.1.1 & I am assuming you aren't referring to any HDP/CDH (Legacy) or CDP Platforms. The Steps to recover Knox Admin Password is more akin to reset of Knox Admin Password & does involve re-provisioning the Certificates and Credentials. This is a fairly risky Operation & we would recommend performing the same with Cloudera Support. The Doc [1] covers the same for your reference. Regards, Smarak [1]Change the Master Secret (cloudera.com)
... View more
09-08-2022
07:25 AM
Hi Jim, thanks for your prompt answer. Here my answers: 1) what do the logs say? nothing relevant, just the illegal argument exception, for example: 2022-09-08 16:15:42,386 WARN server.AuthenticationFilter (AuthenticationFilter.java:doFilter(608)) - Authentication exception: java.lang.IllegalArgumentException 2)Thanks for the information provided, but I am not able to identify if the config is ok or not. One important thing perhaps to mention is that the Yarn Server is in one domain (let´s call it A) but the user authentication is done to a different domain (let´s call it B). For what I see in the headers, the server side and the client side are making reference of domain A, which makes sense, but I can´t identify in which moment the illegal argument comes up 3) the domain controllers were deprecated, and we had to reconfigure the Kerberos information by the servers in the Cluster plus run the Ambari Ldap Setup to make reference to the new DC. We did not modify anything regarding Yarn, Oozie or the other services. Thanks for your help, Jesus
... View more