ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yesha Vora (JIRA)" <>
Subject [jira] [Created] (AMBARI-17148) Fix rm.audit.logger and nm.audit.logger configuration setting for Yarn
Date Thu, 09 Jun 2016 19:18:21 GMT
Yesha Vora created AMBARI-17148:

             Summary: Fix rm.audit.logger and nm.audit.logger configuration setting for Yarn
                 Key: AMBARI-17148
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.4.0
            Reporter: Yesha Vora
            Priority: Critical

Ambari sets RMAUDIT and NMAUDIT loggers by default for YARN. 

This config leads to log4j errors while running yarn-cli command. 
 yarn application -list
log4j:ERROR setFile(null,true) call failed. /xx/nm-audit.log (No such file or directory)
	at Method)
	at org.apache.log4j.FileAppender.setFile(
	at org.apache.log4j.FileAppender.activateOptions(
	at org.apache.log4j.DailyRollingFileAppender.activateOptions(
	at org.apache.log4j.config.PropertySetter.activate(
	at org.apache.log4j.config.PropertySetter.setProperties(
	at org.apache.log4j.config.PropertySetter.setProperties(
	at org.apache.log4j.PropertyConfigurator.parseAppender(
	at org.apache.log4j.PropertyConfigurator.parseCategory(
	at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers({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

View raw message