[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279419#comment-13279419 ] Hudson commented on HBASE-6010: --- Integrated in HBase-0.94-security #27 (See [https://builds.apache.org/job/HBase-0.94-security/27/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339819) Result = SUCCESS apurtell : Files : * /hbase/branches/0.94/bin/hbase * /hbase/branches/0.94/bin/hbase-daemon.sh * /hbase/branches/0.94/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- 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
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278247#comment-13278247 ] Hudson commented on HBASE-6010: --- Integrated in HBase-TRUNK #2893 (See [https://builds.apache.org/job/HBase-TRUNK/2893/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339817) Result = SUCCESS apurtell : Files : * /hbase/trunk/bin/hbase * /hbase/trunk/bin/hbase-daemon.sh * /hbase/trunk/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- 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
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278253#comment-13278253 ] Hudson commented on HBASE-6010: --- Integrated in HBase-0.94 #195 (See [https://builds.apache.org/job/HBase-0.94/195/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339819) Result = SUCCESS apurtell : Files : * /hbase/branches/0.94/bin/hbase * /hbase/branches/0.94/bin/hbase-daemon.sh * /hbase/branches/0.94/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- 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
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278426#comment-13278426 ] Hudson commented on HBASE-6010: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339817) Result = FAILURE apurtell : Files : * /hbase/trunk/bin/hbase * /hbase/trunk/bin/hbase-daemon.sh * /hbase/trunk/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- 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
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276994#comment-13276994 ] Andrew Purtell commented on HBASE-6010: --- I'm going to commit this in a little while if there are no objections. I tested this on a Hadoop 1.0.2 + HBase 0.94.0 cluster and the audit messages showed up in the right file at the right location. Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- 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
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276424#comment-13276424 ] Hadoop QA commented on HBASE-6010: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12527549/6010.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. 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. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 31 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster org.apache.hadoop.hbase.master.TestSplitLogManager Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1883//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1883//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1883//console This message is automatically generated. Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- 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
