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

[mike]

Just got a ton of these on the proxy:

2008/05/02 00:39:18 [error] 30191#0: *88449678 upstream timed out
(110: Connection timed out) while reading response header from
upstream

Not anything in the upstream error log - but it looks like NFS might
have frozen.

Shouldn't the upstream's error log report something about failure to
read a file or something?


On 5/1/08, Igor Sysoev <is at rambler-co.ru> wrote:
> On Wed, Apr 30, 2008 at 11:55:32PM -0700, mike wrote:
>
> > Not that time, I think ever since I did the ignore client aborts/etc I
> > don't get the corresponding errors.
>
> You should look upstream errors on proxy nginx side and client errors
> on other nginx side: the proxy nginx is client for nginxes of second level.
>
> > On 4/30/08, Igor Sysoev <is at rambler-co.ru> wrote:
> > > On Wed, Apr 30, 2008 at 11:27:21PM -0700, mike wrote:
> > >
> > > > On 4/30/08, Igor Sysoev <is at rambler-co.ru> wrote:
> > > >
> > > > > What do you mean by manually ?
> > > >
> > > > I mean I loaded it manually in my browser to double check it loads,
> > > > and there is no handler on that vhost that does fastcgi no matter what
> > > > either.
> > >
> > > Are the corresponding messages on other nginx ?
> > >
> > >
> > > --
> > > Igor Sysoev
> > > http://sysoev.ru/en/
> > >
> > >
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
>