Project

Profile

Help

Issue #1739

closed

content wsgi app does not log errors

Added by jsherril@redhat.com about 8 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
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:
No
Sprint Candidate:
No
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.

Also available in: Atom PDF