<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Hadoop suppress security logger log level in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Hadoop-suppress-security-logger-log-level/m-p/380549#M244084</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/99054"&gt;@akshaydalvi&lt;/a&gt;&amp;nbsp;, I am not sure if you are using Cloudera Manager or not. Please confirm. Make sure your log4j.properties reflects what you are trying to change. You could add "hadoop.security.logger=ERROR,RFAS" line under the log4j safety valve. Be sure that you are using the right RollingAppender name RFA or RFAS. We generally use RFAS for SecurityLogger as shown below snippet.&lt;/P&gt;&lt;LI-CODE lang="java"&gt;hadoop.security.log.file=SecurityAuth-${user.name}.audit
log4j.appender.RFAS=org.apache.log4j.RollingFileAppender
log4j.appender.RFAS.File=/var/log/hadoop-hdfs/SecurityAuth-${user.name}.audit&lt;/LI-CODE&gt;&lt;P&gt;Here is how we configure the log4j safety valve in Cloudera Manager under HDFS -&amp;gt; Configuration&lt;/P&gt;&lt;P&gt;@&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2023-12-08 at 6.17.41 PM.png" style="width: 999px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/39145i6F2A6FF5A31C58C5/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2023-12-08 at 6.17.41 PM.png" alt="Screenshot 2023-12-08 at 6.17.41 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Dec 2023 13:00:05 GMT</pubDate>
    <dc:creator>Majeti</dc:creator>
    <dc:date>2023-12-08T13:00:05Z</dc:date>
    <item>
      <title>Hadoop suppress security logger log level</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Hadoop-suppress-security-logger-log-level/m-p/379910#M243955</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I want to change the log level of the Hadoop security logger from INFO to ERROR. I've exported the following environment variable for that&lt;/P&gt;&lt;P&gt;&lt;EM&gt;export HADOOP_NAMENODE_OPTS="-Dhadoop.security.logger=ERROR,RFA ${HADOOP_NAMENODE_OPTS}"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;I can see the new parameter has been reflected in the command line&lt;/P&gt;&lt;P&gt;&lt;EM&gt;hdfs 13048 2.1 0.7 3899916 509000 ? Sl 01:22 0:29 /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Dproc_namenode -Djava.net.preferIPv4Stack=true -Dhdfs.audit.logger=INFO,NullAppender &lt;STRONG&gt;-Dhadoop.security.logger=ERROR,RFA&lt;/STRONG&gt; -Dyarn.log.dir=/var/log/hadoop-hdfs -Dyarn.log.file=hadoop-hdfs-namenode-hadoop-master-1.log -Dyarn.home.dir=/usr/lib/hadoop-yarn -Dyarn.root.logger=INFO,console -Djava.library.path=/usr/lib/hadoop/lib/native -Xmx2048m -Dhadoop.log.dir=/var/log/hadoop-hdfs -Dhadoop.log.file=hadoop-hdfs-namenode-hadoop-master-1.log -Dhadoop.home.dir=/usr/lib/hadoop -Dhadoop.id.str=hdfs -Dhadoop.root.logger=ERROR,RFA -Dhadoop.policy.file=hadoop-policy.xml org.apache.hadoop.hdfs.server.namenode.NameNode&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;But still, I can see the INFO level logs from the security logger in the log file&lt;/P&gt;&lt;P&gt;&lt;EM&gt;[Socket Reader #1 for port 9820] INFO SecurityLogger.org.apache.hadoop.ipc.Server - Auth successful for hdfs/hadoop-master-1.hadoop.default.svc.cluster.local@CLUSTER.LOCAL (auth:KERBEROS)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;[Socket Reader #1 for port 9820] INFO SecurityLogger.org.apache.hadoop.security.authorize.ServiceAuthorizationManager - Authorization successful for hdfs/hadoop-master-1.hadoop.default.svc.cluster.local@CLUSTER.LOCAL (auth:KERBEROS) for protocol=interface org.apache.hadoop.ha.HAServiceProtocol&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Anything I'm missing here?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 06:51:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Hadoop-suppress-security-logger-log-level/m-p/379910#M243955</guid>
      <dc:creator>akshaydalvi</dc:creator>
      <dc:date>2023-11-30T06:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Hadoop suppress security logger log level</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Hadoop-suppress-security-logger-log-level/m-p/380549#M244084</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/99054"&gt;@akshaydalvi&lt;/a&gt;&amp;nbsp;, I am not sure if you are using Cloudera Manager or not. Please confirm. Make sure your log4j.properties reflects what you are trying to change. You could add "hadoop.security.logger=ERROR,RFAS" line under the log4j safety valve. Be sure that you are using the right RollingAppender name RFA or RFAS. We generally use RFAS for SecurityLogger as shown below snippet.&lt;/P&gt;&lt;LI-CODE lang="java"&gt;hadoop.security.log.file=SecurityAuth-${user.name}.audit
log4j.appender.RFAS=org.apache.log4j.RollingFileAppender
log4j.appender.RFAS.File=/var/log/hadoop-hdfs/SecurityAuth-${user.name}.audit&lt;/LI-CODE&gt;&lt;P&gt;Here is how we configure the log4j safety valve in Cloudera Manager under HDFS -&amp;gt; Configuration&lt;/P&gt;&lt;P&gt;@&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2023-12-08 at 6.17.41 PM.png" style="width: 999px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/39145i6F2A6FF5A31C58C5/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2023-12-08 at 6.17.41 PM.png" alt="Screenshot 2023-12-08 at 6.17.41 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2023 13:00:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Hadoop-suppress-security-logger-log-level/m-p/380549#M244084</guid>
      <dc:creator>Majeti</dc:creator>
      <dc:date>2023-12-08T13:00:05Z</dc:date>
    </item>
  </channel>
</rss>

