[
https://issues.apache.org/jira/browse/AMBARI-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327528#comment-15327528
]
Hadoop QA commented on AMBARI-17148:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809856/AMBARI-17148.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7319//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7319//console
This message is automatically generated.
> Fix rm.audit.logger and nm.audit.logger configuration setting for Yarn
> ----------------------------------------------------------------------
>
> Key: AMBARI-17148
> URL: https://issues.apache.org/jira/browse/AMBARI-17148
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Yesha Vora
> Priority: Critical
> Attachments: AMBARI-17148.patch
>
>
> Ambari sets RMAUDIT and NMAUDIT loggers by default for YARN.
> {code}rm.audit.logger=INFO,RMAUDIT
> ..
> nm.audit.logger=INFO,NMAUDIT
> ..{code}
> This config leads to log4j errors while running yarn-cli command.
> {code}
> yarn application -list
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /xx/nm-audit.log (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:133)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:223)
> at
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
> at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672){code}
> In YARN's case, rm.audit.logger should be set when starting RM only and
> nm.audit.logger when starting NMs only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
