Issue #1739: content wsgi app does not log errors - Pulp

Actions

Send by e-mail Copy link

Issue #1739

closed

content wsgi app does not log errors

Added by jsherril@redhat.com about 7 years ago. Updated almost 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

High

Assignee:

jcline@redhat.com

Category:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

4. Urgent

Version:

Master

Platform Release:

2.8.0

OS:

CentOS 7

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Pulp 2

Sprint:

Quarter:

Description

When hitting errors with the content app, no errors are logged even for 500 ISE's.

The only way to see any sort of error is to change DEBUG to true in /pulp/server/content/web/settings.py and restart apache. At that point making a request will show the error as part of the response, but it still is not logged.

Actions

Copy link

Updated by mhrivnak about 7 years ago

Priority changed from Normal to High
Severity changed from 2. Medium to 4. Urgent
Platform Release set to 2.8.1
Triaged changed from No to Yes

Actions

Copy link

Updated by jcline@redhat.com about 7 years ago

Status changed from NEW to ASSIGNED
Assignee set to jcline@redhat.com

Actions

Copy link

Updated by jcline@redhat.com about 7 years ago

Status changed from ASSIGNED to POST

https://github.com/pulp/pulp/pull/2473

Added by Jeremy Cline about 7 years ago

Revision 9af1dcf0

Enable logging for the content.wsgi application.

This commit configures loggers for the content.wsgi application. This ensures unhandled exceptions are logged to syslog and that logging is configured so messages can be sent from the views.

closes #1739

Added by Jeremy Cline about 7 years ago

Revision 9af1dcf0

Enable logging for the content.wsgi application.

This commit configures loggers for the content.wsgi application. This ensures unhandled exceptions are logged to syslog and that logging is configured so messages can be sent from the views.

closes #1739

Actions

Copy link