hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7740) security audit logger is not on by default, fix the log4j properties to enable the logger
Date Mon, 31 Oct 2011 22:37:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140635#comment-13140635
] 

Aaron T. Myers commented on HADOOP-7740:
----------------------------------------

bq. tested on a secure deploy namenode and jobtracker both have the security logs working.

Did you do this test on trunk? Or only on branch-0.20-security?

On trunk, running a client command (built from source checkout) now results in this:

{noformat}
$ hadoop fs -ls /
log4j:ERROR Could not find value for key log4j.appender.NullAppender
log4j:ERROR Could not instantiate appender named "NullAppender".
{noformat}

Reverting this patch fixes the issue. Could someone please look into this?
                
> security audit logger is not on by default, fix the log4j properties to enable the logger
> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7740
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7740
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.20.205.0
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>            Priority: Minor
>             Fix For: 0.20.205.1, 0.23.0
>
>         Attachments: HADOOP-7740.branch-0.20-security.patch, HADOOP-7740.branch-0.20-security.patch,
HADOOP-7740.branch-0.20-security.patch, HADOOP-7740.branch-0.20-security.patch, HADOOP-7740.branch-0.20-security.patch,
HADOOP-7740.patch, HADOOP-7740.patch, HADOOP-7740.patch, HADOOP-7740.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message