timeout with UWSGI?

[Alex Hall]

We may be finding the problem... I'm not sure what you mean by 'upstream
service'. I know I have an upstream context for PHP, which defines the
socket file to use, but I don't have that for UWSGI. The sample
configurations I found never said to include one, and I don't have a deep
enough grasp of how all this works to know what to put in one for UWSGI.
I'll certainly start looking this up, though.

On Tue, May 10, 2016 at 4:30 PM, Francis Daly <francis at daoine.org> wrote:

> On Tue, May 10, 2016 at 03:29:24PM -0400, Alex Hall wrote:
>
> Hi there,
>
> > Sometimes, by the time it does this, Nginx has given up on
> > it, so I see an IOError reported in the log because of a broken pipe. I'm
> > wondering how I can increase the timeout limit, to make Nginx wait longer
> > before closing this connection? Thanks!
>
> What directive do you use to tell nginx to talk to the upstream service?
>
> Put that directive after "http://nginx.org/r/", and visit that url. That
> should bring you to the documentation for that directive.
>
> Go to the top of the page; there is a list of all of the other directives
> that that module provides.
>
> Probably you care about the "read timeout" directive: you can invite nginx
> to wait longer between successive successful read operations; or you can
> configure your upstream service to write something more frequently that
> it currently does.
>
> Good luck with it,
>
>         f
> --
> Francis Daly        francis at daoine.org
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



-- 
Alex Hall
Automatic Distributors, IT department
ahall at autodist.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160510/467a4a99/attachment.html>