10% 500 Errors

[James Golick]

Scratch that, it's already at debug, and you're right, those errors are at
info level.

Nginx will always log an error when there's a 500?

On Mon, Mar 10, 2008 at 9:53 AM, James Golick <jamesgolick at gmail.com> wrote:

> Okay, I'll change it back.
>
> What should I set my log level to to determine which type of error it is?
>
> J.
>
>
> On Mon, Mar 10, 2008 at 9:49 AM, Igor Sysoev <is at rambler-co.ru> wrote:
>
> > On Mon, Mar 10, 2008 at 09:12:35AM -0400, James Golick wrote:
> >
> > > I have nginx running as a proxy to about twelve upstream app servers,
> > > serving a rails app. Nothing else really in this configuration.
> > >
> > > I am seeing about 10% of requests throwing 500 errors, and this in my
> > error
> > > log:
> > >
> > > 2008/03/10 08:41:05 [info] 6632#0: *12005 client closed prematurely
> > > connection while sending response to client, client: xxx, server: xxx,
> > > request: xxx, host: xxx, referrer: xxx
> > >
> > > I'm also seeing lots of:
> > >
> > > client xxx closed keepalive connection
> > >
> > > but that strikes me as normal, and I'm seeing:
> > >
> > > client closed prematurely connection while reading client request
> > line,
> > > client: xxx, server: xxx
> > >
> > > I have googled far and wide, and the best answers I came up with were
> > to add
> > > these lines to my conf:
> > >
> > > proxy_ignore_client_abort  on;
> > > proxy_next_upstream error;
> >
> > The default
> >
> > proxy_next_upstream error timeout invalid_header;
> >
> > is better.
> >
> > > but, that doesn't seem to have solved the problem.
> > >
> > > Any ideas?
> >
> > Do you see 500, 502, or 504 errors ? They are very different things.
> > Any messages logged at info level is not caused by 50X error.
> >
> >
> > --
> > Igor Sysoev
> > http://sysoev.ru/en/
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080310/6fd90956/attachment.html>