accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ACCUMULO-3450) Example logging configs should disable audit log to application log files
Date Wed, 24 Dec 2014 20:55:13 GMT

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

Keith Turner edited comment on ACCUMULO-3450 at 12/24/14 8:54 PM:
------------------------------------------------------------------

I have been looking into this recently, trying to determine whats going on.  In 1.6.1 and
1.6.2-SNAPSHOT auditLog.xml seems to have no impact.  Not sure if it worked in 1.6.0?

I added {{-Dlog4j.debug}} to the tsever jvm opts and also added some printlns to Accumulo.java.
  It seems like the following is happening.

 1. Initialization is done using generic_logger.xml (can see this from  {{-Dlog4j.debug}}
output
 2. Initialization is done using auditLog.xml (can see this from  {{-Dlog4j.debug}} output
 3. At this point additivity for {{Audit}} is false and its level is OFF  (based on a printlin
in Accumulo.java, can also see setting change from  {{-Dlog4j.debug}} output)
 4. Not sure what causes this, but based on ouput from  {{-Dlog4j.debug}} it seems like initialization
is done again using generic_logger.xml 
 5. At some point after this additivity for {{Audit}} is true its level is not OFF.

Maybe step 4 blows away the config changes made in step 3, not sure.


was (Author: kturner):
I have been looking into this recently, trying to determine whats going on.  In 1.6.1 and
1.6.2-SNAPSHOT auditLog.xml seems to have no impact.  Not sure if it worked in 1.6.0?

I added {{-Dlog4j.debug}} to the tsever jvm opts and also added some printlns to JVM debugging.
  It seems like the following is happening.

 1. Initialization is done using generic_logger.xml (can see this from  {{-Dlog4j.debug}}
output
 2. Initialization is done using auditLog.xml (can see this from  {{-Dlog4j.debug}} output
 3. At this point additivity for {{Audit}} is false and its level is OFF  (based on a printlin
in Accumulo.java, can also see setting change from  {{-Dlog4j.debug}} output)
 4. Not sure what causes this, but based on ouput from  {{-Dlog4j.debug}} it seems like initialization
is done again using generic_logger.xml 
 5. At some point after this additivity for {{Audit}} is true its level is not OFF.

Maybe step 4 blows away the config changes made in step 3, not sure.

> Example logging configs should disable audit log to application log files
> -------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3450
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3450
>             Project: Accumulo
>          Issue Type: Bug
>          Components: start
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: 1.7.0
>
>
> The presence of an auditLog.xml file controls the "audit" log for incoming clients, security
operations, etc. Because a normal logger instance is used for this purpose, it also gets dumped
into the normal application log files (e.g. $process_$host.[debug.]log).
> We should turn off the audit log in the generic_logger configuration and let auditLog.xml
create the log file specifically for audits when the user configures it as such (as the audit
log is intended to be off by default by virtue of the example configuration files we generate).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message