10% 500 Errors

James Golick jamesgolick at gmail.com
Mon Mar 10 17:38:23 MSK 2008


Still says 200. Somebody is throwing this error and won't admit to it. I'm
guessing it's mongrel, but at this point, I've really got no idea.

On Mon, Mar 10, 2008 at 10:28 AM, Igor Sysoev <is at rambler-co.ru> wrote:

> On Mon, Mar 10, 2008 at 10:18:53AM -0400, James Golick wrote:
>
> > That's the really weird thing - nothing.
> >
> > It seems like maybe my upstream is responding with 200, but actually
> showing
> > a 500-style error?
>
> You may log $upstream_status in access_log to see an exact upstream
> status.
>
> > On Mon, Mar 10, 2008 at 10:10 AM, Igor Sysoev <is at rambler-co.ru> wrote:
> >
> > > On Mon, Mar 10, 2008 at 10:06:27AM -0400, James Golick wrote:
> > >
> > > > Nothing.
> > > >
> > > > I'm thinking now that these must be coming occasionally from my
> upstream
> > > > servers.
> > >
> > > I mean what do you see in access_log - 500, 502, etc ?
> > >
> > > > Thanks for your help
> > > >
> > > > On Mon, Mar 10, 2008 at 10:02 AM, Igor Sysoev <is at rambler-co.ru>
> wrote:
> > > >
> > > > > On Mon, Mar 10, 2008 at 09:55:23AM -0400, James Golick wrote:
> > > > >
> > > > > > Nginx will always log an error when there's a 500?
> > > > >
> > > > > Yes, at least I have tried to log them all. The log is single way
> > > > > to know about the problems.
> > > > >
> > > > > So what do you see - 500, 502, 503, or 504 ?
> > > > >
> > > > >
> > > > > --
> > > > > Igor Sysoev
> > > > > http://sysoev.ru/en/
> > > > >
> > > > >
> > >
> > > --
> > > Igor Sysoev
> > > http://sysoev.ru/en/
> > >
> > >
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080310/f3c448ea/attachment.html>


More information about the nginx mailing list