Hello!

On Tue, Aug 20, 2013 at 1:26 PM, Maxim Dounin <mdounin@mdounin.ru> wrote:

> 2013/08/20 09:34:31 [debug] 1692#0: *1101651 http upstream process non buffered downstream
> 2013/08/20 09:34:31 [info] 1692#0: *1101651 client timed out (110: Connection timed out) while sending to client, client: 80.219.149.116, server: , request: "POST /index.php/winclient/gnegg HTTP/1.0", upstream: "http://127.0.0.1:8081/index.php/winclient/gnegg", host: "REDACTED.popscan.ch"
> 2013/08/20 09:34:31 [debug] 1692#0: *1101651 finalize http upstream request: 408
>
> After a 60 seconds timer was fired and client connection was
> closed as timed out.

Yeah. That's what I feared. But the connection was definitely still
open and data was being transferred.


> Unfortunately, with location-level debug logs it's not possible to
> see event handling details (and that's why it's generally
> recommended to activate debug log at global level, BTW).

any idea how to do this on a system that's under load (60 requests per
second)? As I said before: When I do the same request on a system
that's not under load, the problem doesn't appear.

> But I would suppose everything is fine there as well, and the problem is
> actually a result of kernel's behaviour.

I started suspecting as much. Any pointers how I could work around/fix
the issue on the kernel level?

Philip


--
Sensational AG
Giesshübelstrasse 62c, Postfach 1966, 8021 Zürich
Tel. +41 43 544 09 60, Mobile +41 79 341 01 99
info@sensational.ch, http://www.sensational.ch

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx