502 error after adding module to a Django project running on nginx and gunicorn

Question

I am trying to add a module to an existing Django project, but once I have done it I get a 502 error. The server is running Ubuntu. I don't think it has to do with the applications code because I got it running on the django development server. It goes away when I take out the app's name from settings.py and restart gunicorn.

Here's a part of the log

2011/07/15 01:24:45 [error] 16136#0: *75593 connect() failed (111: Connection refused)   while connecting to upstream, client: 24.17.8.152, server: staging.site.org, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8020/", host: "staging.site.org"

Here's the nginx config file. Nginx Config File

I'm not sure what other information is needed. Not sure where the gunicorn logs are located. My server admin skills are kind of lacking. What sort of things should I be doing to figure out where the problem is starting.

Answer 1

Probably there is an error in the module which causing django application to fail completely. Check if it is running at all.

Answer 2

I don't know if this will apply to you, but I had a similar issue using nginx and passenger, and I wasn't including my django root directory (the one with manage.py/settings.py/etc) in my work path. I've not worked with gunicorn, but is it possible you need to add sys.path.append on that directory somewhere in your gunicorn configuration?