Bug 787086 - Configure logging output correctly
Summary: Configure logging output correctly
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: PulpDist
Classification: Community
Component: Web App
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 0.1.0
Assignee: Nick Coghlan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-03 05:53 UTC by Nick Coghlan
Modified: 2012-02-07 05:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 05:17:26 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nick Coghlan 2012-02-03 05:53:34 UTC 
Currently, the pulpdist-httpd RPM correctly creates /var/log/pulpdist, but pulpdist.django_site doesn't actually set up any stream handler to write there (instead just logging to the console and relying on Apache being set up to log console output from applications)

This needs to be fixed so that misbehaviour can be diagnosed sanely...
Comment 1 Nick Coghlan 2012-02-07 05:17:26 UTC 
Now creates 5 log files (some messages appear in multiple locations):

Split by namespace (all DEBUG+):
  pulpdist.log
  pulp.log
  django.log

Split by severity (django, pulp and pulpdist namespaces):
  debug.log
  error.log
Note You need to log in before you can comment on or make changes to this bug.