10% 500 Errors

[Phillip B Oldham]

Could it be a permission problem? i.e. something's trying to write to an 
empty log but doesn't have permission, so dies without telling anyone?

James Golick wrote:
> It isn't. There's absolutely nothing in the production log.
>
> On Mon, Mar 10, 2008 at 11:28 AM, Dave Cheney <dave at cheney.net 
> <mailto:dave at cheney.net>> wrote:
>
>     Not that I know of, but the root cause appears to be an uncaught
>     exception in the exception handler code.
>
>     The failsafe code in dispatcher.rb is utterly obfuscated, one of
>     the guys in our team has patched it to return 500 properly, but
>     that hasn't been submitted back to rails core.
>
>     Regardless, the REAL cause of the exception will be in your
>     production.log.
>
>     Cheers
>
>     Dave
>
>     On 11/03/2008, at 2:16 AM, James Golick wrote:
>
>>     Dave - is there any common reason that might be happening
>>     intermittently on just about any controller/action combination
>>     for an app?
>>
>>     On Mon, Mar 10, 2008 at 11:04 AM, Aníbal Rojas
>>     <anibalrojas at gmail.com <mailto:anibalrojas at gmail.com>> wrote:
>>
>>         James,
>>
>>            As some kind of "last resource"...
>>
>>            What about hacking a quick controller to respond with the
>>         offending codes and check how are they being handled?
>>
>>         --
>>         Aníbal
>>
>>         On Tue, Mar 11, 2008 at 10:08 AM, James Golick
>>         <jamesgolick at gmail.com <mailto:jamesgolick at gmail.com>> wrote:
>>         > 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 <mailto: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 <mailto: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 <mailto: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/
>>         > >
>>         > >
>>
>>
>
>

-- 

*Phillip B Oldham*
The Activity People
phill at theactivitypeople.co.uk <mailto:phill at theactivitypeople.co.uk>

------------------------------------------------------------------------

*Policies*

This e-mail and its attachments are intended for the above named 
recipient(s) only and may be confidential. If they have come to you in 
error, please reply to this e-mail and highlight the error. No action 
should be taken regarding content, nor must you copy or show them to anyone.

This e-mail has been created in the knowledge that Internet e-mail is 
not a 100% secure communications medium, and we have taken steps to 
ensure that this e-mail and attachments are free from any virus. We must 
advise that in keeping with good computing practice the recipient should 
ensure they are completely virus free, and that you understand and 
observe the lack of security when e-mailing us.

------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080310/ba529359/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phill.vcf
Type: text/x-vcard
Size: 261 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx/attachments/20080310/ba529359/attachment.vcf>