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.

Did you try changing your dir permission? it worked for me. – Aswin Nov 07 '15 at 11:18 — Aswin, Nov 07 '15 at 11:18

score 1 · Answer 1 · answered Jul 15 '11 at 17:17

1

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

answered Jul 15 '11 at 17:17

rvs

4,125
1
27
31

I'm not used to much server admin. How would I check if it is running? – thebeagle Jul 15 '11 at 18:57

score 1 · Answer 2 · answered Jul 31 '12 at 01:27

1

How did you install the new module? If you installed it on your dev machine using pip, apt-get, etc., make sure you do the same on your server.

answered Jul 31 '12 at 01:27

mdashx

111
2

score 0 · Answer 3 · answered Jan 17 '12 at 17:14

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?

score 0 · Answer 4 · answered Jul 31 '12 at 01:36

Connection refused is a pretty obvious one. It means your backend (in this case, gunicorn) is not running on the port you've specified in your nginx config (in this case, 8020).

One of two things is going on here. Either:

gunicorn is running on a different port, or
gunicorn is not running.

If you're sure this is the right port, then try starting gunicorn.

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

4 Answers4