Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A9C510173 for ; Tue, 18 Feb 2014 05:04:28 +0000 (UTC) Received: (qmail 81928 invoked by uid 500); 18 Feb 2014 05:04:27 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 81845 invoked by uid 500); 18 Feb 2014 05:04:23 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 81833 invoked by uid 99); 18 Feb 2014 05:04:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Feb 2014 05:04:20 +0000 Date: Tue, 18 Feb 2014 05:04:19 +0000 (UTC) From: "Vikram Srivastava (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2373) Daemons should be able to log if log4j.properties specifies sufficient logging MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903782#comment-13903782 ] Vikram Srivastava commented on ACCUMULO-2373: --------------------------------------------- bq. The fix for when no matching *_logger.xml is present, we probably don't need to start the thread which I think would fix the issue your raised. I think if you do this, log4j would start using the properties file as it did before for logging and would take care of the other issue as well. So, I'm fine with your proposal. > Daemons should be able to log if log4j.properties specifies sufficient logging > ------------------------------------------------------------------------------ > > Key: ACCUMULO-2373 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2373 > Project: Accumulo > Issue Type: Bug > Reporter: Vikram Srivastava > Attachments: log4j.properties > > > Before this commit: > commit 0351d0d416df51f0b10d91acdc074dced36e40d4 > Author: Josh Elser > Date: Mon Feb 10 23:28:31 2014 -0500 > ACCUMULO-2334 Remove ACCUMULO_LOG_HOST in favor of pull host and port log-forwarding from zookeeper > I was able to do logging with only log4j.properties. However, that doesn't work anymore. All my daemons have this as the last line of their logs: > {noformat} > 2014-02-14 14:23:38,049 INFO org.apache.accumulo.server.Accumulo: Zookeeper connected and initialized, attemping to talk to HDFS > 2014-02-14 14:23:38,067 INFO org.apache.accumulo.server.watcher.MonitorLog4jWatcher: Changing monitor log4j address to 10.20.93.170:4560 > 2014-02-14 14:23:38,067 INFO org.apache.accumulo.server.watcher.MonitorLog4jWatcher: Enabled log-forwarding > {noformat} > Note that I don't use generic_logger.xml, and this wasn't a requirement for 1.4. But now it seems there is no logging if *_logger.xml files are not present (as ACCUMULO-2349 has also reported). -- This message was sent by Atlassian JIRA (v6.1.5#6160)