Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to serve a Django app using gunicorn. In my current setup running on Debian 6 (production) and Ubuntu 11.04 (development), gunicorn (v0.12) is behind nginx and managed by supervisor. The setup runs OK, except that exceptions are not logged.

It is the same if I run gunicorn from the command line: run_gunicorn Again there's no output. The problem applies only to ERROR-level events, INFO-level output is produced when workers get started. The traceback is displayed on the page if DEBUG = True.

The app runs on Django v1.3 with no changes in the default logging settings.

Today v0.13 featuring a refactor of logging has become available, but the issue is still there.

I'd very much appreciate any help.

Edit: I got error emailing working, it is irrelevant to the logging issue.

share|improve this question
Handle the logging with a logger in the application code, instead of expecting the server to do it for you. – Tom O'Connor Dec 2 '11 at 22:05

Do you mean that you get no log message upon an error 500? After about 30 seconds into a request? In that case, gunicorn killed off its child process that was serving you. And it kills in a quick and hard way that leaves no logging.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.