daydreamer
daydreamer

Reputation: 91949

How to debug gunicorn failure issues? (Worker failed to boot)

I have a Django web application that uses Gunicorn and runs good locally, but when I deploy app on EC2, I see that Gunicorn is failing:

 $ gunicorn_django -b 127.0.0.1:8000 --settings=myapp.settings.dev --debug --log-level info
 2012-09-16 17:39:24 [28333] [INFO] Starting gunicorn 0.14.6
 2012-09-16 17:39:24 [28333] [INFO] Listening at: http://127.0.0.1:8000 (28333)
 2012-09-16 17:39:24 [28333] [INFO] Using worker: sync
 2012-09-16 17:39:24 [28336] [INFO] Booting worker with pid: 28336
 2012-09-16 17:39:24 [28336] [INFO] Worker exiting (pid: 28336)
 2012-09-16 17:39:24 [28333] [INFO] Shutting down: Master
 2012-09-16 17:39:24 [28333] [INFO] Reason: Worker failed to boot.

I tried logging with --spew but it keeps on running and no error is shown.

How can I debug this issue?

Upvotes: 35

Views: 39302

Answers (3)

David Fraser
David Fraser

Reputation: 7439

Try running with --preload as an argument to gunicorn_django - it should show you the error the workers are having when starting. See this bug

Upvotes: 47

mik.ro
mik.ro

Reputation: 4883

In my case I had to run gunicorn_django --bind example.com:8001 from the same folder as my manage.py file.

Upvotes: 7

Ben Davis
Ben Davis

Reputation: 13780

You need --debug --log-level debug

Upvotes: 29

Related Questions