>From your logs it looks like you are using HDP. and the audit.xml file is not in CLASSPATH what version of HDP you r using
this link is for ranger installation on HDP2.2 http://hortonworks.com/blog/apache-ranger-audit-framework/ make sure you have followed everything, below is the snippet from the earlier link which deals with the placing xml file on correct path. [image: Inline image 1] *RegardsMuthupandi.K* Think before you print. On Fri, Mar 6, 2015 at 2:55 PM, Hadoop Solutions <[email protected]> wrote: > Hi Mathu, > > Please find the attached NN log. > > i have copied all jar to /usr/hdp/current/hadoop-hdfs-namenode/lib > location. > > please provide me the right solution for this issue. > > Thanks, > Shaik > > On 6 March 2015 at 15:48, Muthu Pandi <[email protected]> wrote: > >> Could you post the logs of your Active NN or the NN where you deployed >> your Ranger >> >> Also Make sure you have copied your JARS to respective folders and >> restarted the cluster. >> >> >> >> *RegardsMuthupandi.K* >> >> Think before you print. >> >> >> >> On Fri, Mar 6, 2015 at 1:08 PM, Hadoop Solutions <[email protected]> >> wrote: >> >>> Hi Amithsha, >>> >>> I have deployed ranger-hdfs-plugin again with HA NN url. >>> >>> But, i am agents are not listed in Ranger Agents. I am using HDP 2.2. >>> >>> Please advise to resolve this issue. >>> >>> Thanks, >>> Shaik >>> >>> On 6 March 2015 at 14:48, Amith sha <[email protected]> wrote: >>> >>>> Hi Shail, >>>> >>>> Below mentioned steps are mentioned in Ranger Guide to enable Ranger >>>> plugin In Hadoop HA cluster >>>> >>>> >>>> To enable Ranger in the HDFS HA environment, an HDFS plugin must be >>>> set up in each NameNode, and then pointed to the same HDFS repository >>>> set up in the Security Manager. Any policies created within that HDFS >>>> repository are automatically synchronized to the primary and secondary >>>> NameNodes through the installed Apache Ranger plugin. That way, if the >>>> primary NameNode fails, the secondary namenode takes over and the >>>> Ranger plugin at that NameNode begins to enforce the same policies for >>>> access control. >>>> When creating the repository, you must include the fs.default.name for >>>> the primary NameNode. If the primary NameNode fails during policy >>>> creation, you can then temporarily use the fs.default.name of the >>>> secondary NameNode in the repository details to enable directory >>>> lookup for policy creation. >>>> >>>> Thanks & Regards >>>> Amithsha >>>> >>>> >>>> On Fri, Mar 6, 2015 at 12:00 PM, Hadoop Solutions >>>> <[email protected]> wrote: >>>> > Hi, >>>> > >>>> > I have installed Ranger from Git repo and I have started Ranger >>>> console. >>>> > >>>> > I am trying to deploy ranger-hdfs plugin on active NN. But, plugin >>>> agent >>>> > unable to contact with Ranger. >>>> > >>>> > Can you please let me know the right procedure for ranger-hdfs plugin >>>> > deployment on HA NN cluster. >>>> > >>>> > >>>> > Regards, >>>> > Shaik >>>> >>> >>> >> >
