Issue #1739
closed
content wsgi app does not log errors
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.
Updated by mhrivnak about 8 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
Updated by jcline@redhat.com about 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jcline@redhat.com
Updated by jcline@redhat.com about 8 years ago
- Status changed from ASSIGNED to POST
Added by Jeremy Cline about 8 years ago
Added by Jeremy Cline about 8 years ago
Revision 9af1dcf0 | View on GitHub
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
Updated by Anonymous about 8 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|9af1dcf077baac3d9969e0e8621c44b3e4fb37a0.
Updated by jcline@redhat.com about 8 years ago
- Platform Release changed from 2.8.1 to 2.8.0
Updated by dkliban@redhat.com about 8 years ago
- Status changed from MODIFIED to 5
Updated by dkliban@redhat.com about 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Updated by bmbouter almost 4 years ago
- Category deleted (
14)
We are removing the 'API' category per open floor discussion June 16, 2020.
.
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