#180 Get logging to work.
Closed by ralph. Opened by ralph.
ralph/waiverdb get-logging-working  into  master

Download 180.patch

Gunicorn has been swallowing all of our log output in openshift making it
impossible to know what's going on. Tested locally, this gets us output to
stdout from both the flask app and the root logger.

1 new commit added

  • Remove old database before starting.

3 new commits added

  • Don't build and install manpages on el7.
  • Remove old database before starting.
  • Get logging to work.

Hmmm. I thought I fixed this already :grimacing:

But I guess in dev we don't use gunicorn so the behaviour is different...

For one thing, you shouldn't need to treat the Flask app logger separately, I thought that was already turned off so that it would just propagate to the root logger (for simplicity).

I actually thought gunicorn removed all its settings which messed with Python logging many releases ago, to avoid this kind of problem, but maybe not...

Yeah, something up here. Without this change, I got zero information out of that kerberos authn issue. :/

OK. We figured out in channel that passing --enable-stdio-inheritance to gunicorn was the way to go.

Pull-Request has been closed by ralph

Metadata