The content wsgi does not respect logging configuration
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.
#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 . 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.
#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.
Please register to edit this issue