timeout with UWSGI?

[Aleksandar Lazic]

Hi Alex.

Am 11-05-2016 16:01, schrieb Alex Hall:
> Yes, I'm using uwsgi_pass:
> 
> uwsgi_pass 127.0.0.1:9876 [1];

Hm. I think you have send the mail to early ;-)
Please can you read again my mail and add some more lines to your 
answer, thank you.

Best regards
aleks

> On Wed, May 11, 2016 at 9:54 AM, Aleksandar Lazic <al-nginx at none.at>
> wrote:
> 
>> Hi Alex,
>> 
>> Am 11-05-2016 09:24, schrieb Francis Daly:
>> On Tue, May 10, 2016 at 05:09:21PM -0400, Alex Hall wrote:
>> 
>> Hi there,
>> 
>> We may be finding the problem... I'm not sure what you mean by
>> 'upstream
>> service'.
>> 
>> Somehow, you tell nginx to talk to "the next server". It can be with
>> "proxy_pass" or "fastcgi_pass" or, most likely here, "uwsgi_pass".
>> 
>> "the next server" is the upstream, in this context.
>> 
>> And the directive is whichever *_pass you use here.
> 
>  What Francis could mean could be this.
> 
> http://nginx.org/en/docs/http/ngx_http_upstream_module.html
> 
> Some basic concept.
> 
> http://nginx.org/en/docs/http/load_balancing.html
> 
> Maybe you should increase some timeouts in uwsgi
> 
> http://nginx.org/en/docs/http/ngx_http_uwsgi_module.html
>   -> search for timeout.
> 
> There are some info's in the net ;-)
> 
> https://startpage.com/do/search?cmd=process_search&query=nginx+long+running+backend+requests&cat=web&with_language=&with_region=&pl=&ff=&rl=&hmb=1&with_date=y&abp=-1
> 
> Can you please add the output of
> 
> nginx -V
> 
> to your answer and the relevant config.
> 
> Hth & Best regards
> aleks