Re: debugging 504 Gateway Time-out

2016-08-15 Thread Francis Daly
On Sun, Aug 14, 2016 at 08:03:21PM -0400, Larry Martell wrote: > On Tue, Aug 9, 2016 at 10:35 PM, Richard Stanway > wrote: Hi there, > I have some requests that can take a long time to return - the users > can request huge amount of data to be pulled from very large database > tables with comple

Re: debugging 504 Gateway Time-out

2016-08-14 Thread Larry Martell
On Tue, Aug 9, 2016 at 10:35 PM, Richard Stanway wrote: >> generated 0 bytes in 640738 msecs > > I would look into what is causing your backend to take over 10 minutes to > respond to that request. I have some requests that can take a long time to return - the users can request huge amount of dat

Re: debugging 504 Gateway Time-out

2016-08-09 Thread Richard Stanway
> generated 0 bytes in 640738 msecs I would look into what is causing your backend to take over 10 minutes to respond to that request. On Tue, Aug 9, 2016 at 11:09 PM, Larry Martell wrote: > I just set up a django site with nginx and uWSGI. Some pages I go to > work fine, but other fail with a

debugging 504 Gateway Time-out

2016-08-09 Thread Larry Martell
I just set up a django site with nginx and uWSGI. Some pages I go to work fine, but other fail with a 504 Gateway Time-out. I used to serve this site with apache and wsgi and these same pages worked fine. This is what I see in the nginx error log: 2016/08/09 16:40:19 [error] 17345#0: *1 upstream