Project

Profile

Help

Issue #2786

The content wsgi does not respect logging configuration

Added by ehelms@redhat.com over 3 years ago. Updated almost 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.14.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

The ability to log to the console was added recently (https://pulp.plan.io/issues/2548) for the Pulp server. However, this logging configuration was not extended to the content wsgi application that serves up repositories which continues to log strictly to syslog.


Related issues

Related to Pulp - Story #2548: As an administrator, I can configure how pulp logsCLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision a1ed99f3 View on GitHub
Added by Eric D. Helms over 3 years ago

fixes #2786: Allow content application to use console logging

Revision fd325250 View on GitHub
Added by mhrivnak over 3 years ago

Adds comments, PEP8, minor polish to content app logging improvement.

https://pulp.plan.io/issues/2786 re #2786

History

#1 Updated by bmbouter over 3 years ago

  • Related to Story #2548: As an administrator, I can configure how pulp logs added

#2 Updated by bmbouter over 3 years ago

@ehelms: I'm not sure what to do to resolve this. The logging is configured at the .conf file for httpd right? Like this [0]. I don't think we can configure the logger via Python code like we do with all the other processes.

We can confirm that httpd doesn't use the Pulp logger by having it raise an Exception in the Pulp logger and try to start httpd. That would probably be good.

[0]: https://github.com/pulp/pulp/blob/master/server/etc/httpd/conf.d/pulp_apache_24.conf

#4 Updated by ehelms@redhat.com over 3 years ago

bmbouter

I'm not sure I entirely follow your concern or how this is different than the way the Pulp server (also run by httpd as you know) would be logging information. I can say that this fixed my issue but I am likely missing something subtle here.

#5 Updated by ttereshc over 3 years ago

  • Status changed from NEW to POST
  • Assignee set to ehelms@redhat.com
  • Triaged changed from No to Yes

#6 Updated by mhrivnak over 3 years ago

Rebased and polished: https://github.com/pulp/pulp/pull/3095

Logging within our WSGI apps is independent from httpd's logging.

Our REST API WSGI app takes particular measures to setup its logging. When the content app was added, it got a slightly different approach to configuring logging. That divide is I think what led to "console" logging getting added in one place and not the other.

#7 Updated by Anonymous over 3 years ago

  • Status changed from POST to MODIFIED

#8 Updated by pcreech over 3 years ago

  • Platform Release set to 2.14.0

#9 Updated by pcreech over 3 years ago

  • Status changed from MODIFIED to 5

#10 Updated by pcreech over 3 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

#11 Updated by bmbouter almost 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF