Return-Path: Delivered-To: apmail-trafficserver-issues-archive@minotaur.apache.org Received: (qmail 73483 invoked from network); 8 Sep 2010 16:53:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Sep 2010 16:53:54 -0000 Received: (qmail 42974 invoked by uid 500); 8 Sep 2010 16:53:54 -0000 Delivered-To: apmail-trafficserver-issues-archive@trafficserver.apache.org Received: (qmail 42959 invoked by uid 500); 8 Sep 2010 16:53:54 -0000 Mailing-List: contact issues-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@trafficserver.apache.org Delivered-To: mailing list issues@trafficserver.apache.org Received: (qmail 42951 invoked by uid 99); 8 Sep 2010 16:53:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Sep 2010 16:53:54 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Sep 2010 16:53:53 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o88GrWvH006331 for ; Wed, 8 Sep 2010 16:53:33 GMT Message-ID: <30618454.79651283964812909.JavaMail.jira@thor> Date: Wed, 8 Sep 2010 12:53:32 -0400 (EDT) From: "George Paul (JIRA)" To: issues@trafficserver.apache.org Subject: [jira] Commented: (TS-55) Logging: Default settings for diagnostic 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/TS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907305#action_12907305 ] George Paul commented on TS-55: ------------------------------- Suggested changes look fine. I'll check it soon ;-) -G > Logging: Default settings for diagnostic logging > ------------------------------------------------ > > Key: TS-55 > URL: https://issues.apache.org/jira/browse/TS-55 > Project: Traffic Server > Issue Type: Bug > Components: Logging > Affects Versions: 2.0.0a > Environment: All platforms > Reporter: George Paul > Assignee: George Paul > Priority: Minor > Fix For: 2.1.3 > > > Currently the default diagnostic logging settings are as follows in proxy/mgmt2/RecordsConfig.cc : > # O stdout > # E stderr > # S syslog > # L diags.log > > proxy.config.diags.output.diag E > proxy.config.diags.output.debug E > proxy.config.diags.output.status S > proxy.config.diags.output.note S > proxy.config.diags.output.warning S > proxy.config.diags.output.error SE > proxy.config.diags.output.fatal SE > proxy.config.diags.output.alert SE > proxy.config.diags.output.emergency SE > This means regular diagnostics will be logged to syslogd. It has been suggested that syslog logging be disabled due to syslogd locking up the system under heavy load. Instead by default and all diagnostic output go to stderr(E) where the output can be captured by TrafficCop in 'traffic.out'. A new configuration could possibly look like this: > proxy.config.diags.output.diag E > proxy.config.diags.output.debug E > proxy.config.diags.output.status E > proxy.config.diags.output.note E > proxy.config.diags.output.warning E > proxy.config.diags.output.error E > proxy.config.diags.output.fatal E > proxy.config.diags.output.alert E > proxy.config.diags.output.emergency E > -George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.