49

I have Nginx + uWSGI for Python Django app.

I have the following in my nginx.conf:

location / {
    include uwsgi_params;
    uwsgi_pass   127.0.0.1:9001;
    uwsgi_read_timeout 1800;
    uwsgi_send_timeout 300;
    client_header_timeout 300;
    proxy_read_timeout 300;
    index  index.html index.htm;
}

but for long running requests on uWSGI which takes about 1 minute to complete I get a timeout error in Nginx error log as below:

2013/04/22 12:35:56 [error] 2709#0: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xx.xx.xx.xx, server: , request: "GET /entity/datasenders/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:9001", host: "xxx.xx.xx.x"

I have already set the header time out and the uWSGI send/read timeouts to 5 mins, can someone please tell me what I can do to overcome this?

famousgarkin
  • 13,687
  • 5
  • 58
  • 74
anishek
  • 1,675
  • 2
  • 13
  • 19

4 Answers4

81

The configuration that solves the problem is:

location / {
    include uwsgi_params;
    uwsgi_pass   127.0.0.1:9001;
    uwsgi_read_timeout 300;
    index  index.html index.htm;
}

The reason the above configuration in the question did not work for us because unfortunately in our machine multiple paths had nginx.conf file. We were working with the conf at the wrong path.

To correctly figure out which path your nginx is picking up the configuration from run: 

nginx -V  # V is caps

this will have a --conf-path=[] which will tell you exactly from where it is picking up the configuration from.

I recently found the above nginx -V to not give the right info. I will leave the above just in case others find it useful.

famousgarkin
  • 13,687
  • 5
  • 58
  • 74
anishek
  • 1,675
  • 2
  • 13
  • 19
  • 2
    what's that number representing? seconds? and is it going to be a problem if we had it set on a large number like 2000? – senaps Sep 11 '17 at 06:12
5

Solved by changing the following Nginx config

proxy_connect_timeout 300;
proxy_read_timeout    300;


client_body_timeout   300;
client_header_timeout 300;
keepalive_timeout     300;

And UWSGI setting

http-timeout = 300 // or 'socket-timeout = 300' depending on uwsgi setting
vinayak hegde
  • 2,117
  • 26
  • 26
0

In addition to the "uwsgi_read_timeout" answer, you should also check that ownership is correct for your nginx uwsgi cache directory. Ownership must be set to the same user as the running nginx process... In my case I had to do this

grep '^user' /etc/nginx/nginx.conf
ls -lah /var/cache/nginx/uwsgi_temp
for f in $( find /var/cache/nginx/uwsgi_temp ); do ls -lah $f; done

Are these files owned by the same user? If not, you could shut down nginx and remove all the cache files, make sure that the proper owner is on /var/cache/nginx/uwsgi_temp and restart. Maybe you could also just do a recursive chown, I didn't test this approach.

# store the user
THEUSER=$(grep '^user' /etc/nginx/nginx.conf | sed 's/.* //; s/;.*//' )

Remove cache and restart approach

/etc/init.d/nginx stop
rm -rf /var/cache/nginx/uwsgi_temp/* 
chown $THEUSER:$THEUSER /var/cache/nginx/uwsgi_temp
/etc/init.d/nginx start

Recursive chown approach

chown -R $THEUSER:$THEGROUP /var/cache/nginx/uwsgi_temp/
# not sure if you have to restart nginx here...
rideswitch
  • 1,381
  • 2
  • 13
  • 19
0

Looking at the uwsgi error logs and understanding what the problem has helped me. Issue was not related to Nginx configurations at all. My email host has changed and the code threw error while calling the send email code

Lina T
  • 169
  • 2
  • 3