Weird timeouts, not sure if I've set the right threshholds

Igor Sysoev is at rambler-co.ru
Fri May 2 21:35:43 MSD 2008


On Fri, May 02, 2008 at 10:46:44PM +1000, Dave Cheney wrote:

> You have a setup ?
> 
> client -> nginx1 -> nginx2
> 
> so nginx2 is waiting for nginx1 to send it something, but nginx1 is  
> expecting nginx2 to sending it something, nginx2 gets tired of waiting  
> and closes the connection.

No. nginx1 gets all client request, then it connects to nginx2 and
passes full request to it. Then nginx1 wait nginx2 response.

> What are your proxy settings? grep proxy nginx.conf
> 
> Cheers
> 
> Dave
> 
> On 02/05/2008, at 6:28 PM, mike wrote:
> 
> >and lots of these, in groups:
> >
> >2008/05/02 01:26:08 [error] 30190#0: *88628174 recv() failed (104:
> >Connection reset by peer) while reading response header from upstream,
> >client: 52.94.24.43, server: lvs01.myhost.net, request: "GET
> >/i/rate/100/294/100294392_48e1c_h.jpg HTTP/1.1", upstream:
> >"http://10.13.5.10:80/i/rate/100/294/100294392_48e1c_h.jpg", host:
> >"media.client.com", referrer: "http://www.client.com/photos.php"
> >
> >this is from the proxy server error log
> >
> >below were from the upstream error log
> >
> >On 5/2/08, mike <mike503 at gmail.com> wrote:
> >>Here's some weird ones:
> >>
> >>2008/05/02 01:24:37 [info] 6656#0: *562998 client timed out (110:
> >>Connection timed out) while reading client request line, client:
> >>10.13.5.16, server: 0.0.0.0:80
> >>2008/05/02 01:24:38 [info] 6658#0: *563002 client timed out (110:
> >>Connection timed out) while reading client request line, client:
> >>10.13.5.16, server: 0.0.0.0:80
> >>
> >>10.13.5.16 is my proxy server (nginx)
> >
> 

-- 
Igor Sysoev
http://sysoev.ru/en/





More information about the nginx mailing list