Dave - is there any common reason that might be happening intermittently on just about any controller/action combination for an app?<br><br><div class="gmail_quote">On Mon, Mar 10, 2008 at 11:04 AM, Aníbal Rojas <<a href="mailto:anibalrojas@gmail.com" target="_blank">anibalrojas@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">James,<br>
<br>
As some kind of "last resource"...<br>
<br>
What about hacking a quick controller to respond with the<br>
offending codes and check how are they being handled?<br>
<br>
--<br>
<font color="#888888">Aníbal<br>
</font><div><div></div><div><br>
On Tue, Mar 11, 2008 at 10:08 AM, James Golick <<a href="mailto:jamesgolick@gmail.com" target="_blank">jamesgolick@gmail.com</a>> wrote:<br>
> Still says 200. Somebody is throwing this error and won't admit to it. I'm<br>
> guessing it's mongrel, but at this point, I've really got no idea.<br>
><br>
><br>
><br>
> On Mon, Mar 10, 2008 at 10:28 AM, Igor Sysoev <<a href="mailto:is@rambler-co.ru" target="_blank">is@rambler-co.ru</a>> wrote:<br>
><br>
> ><br>
> > On Mon, Mar 10, 2008 at 10:18:53AM -0400, James Golick wrote:<br>
> ><br>
> > > That's the really weird thing - nothing.<br>
> > ><br>
> > > It seems like maybe my upstream is responding with 200, but actually<br>
> showing<br>
> > > a 500-style error?<br>
> ><br>
> > You may log $upstream_status in access_log to see an exact upstream<br>
> status.<br>
> ><br>
> ><br>
> > > On Mon, Mar 10, 2008 at 10:10 AM, Igor Sysoev <<a href="mailto:is@rambler-co.ru" target="_blank">is@rambler-co.ru</a>> wrote:<br>
> > ><br>
> > > > On Mon, Mar 10, 2008 at 10:06:27AM -0400, James Golick wrote:<br>
> > > ><br>
> > > > > Nothing.<br>
> > > > ><br>
> > > > > I'm thinking now that these must be coming occasionally from my<br>
> upstream<br>
> > > > > servers.<br>
> > > ><br>
> > > > I mean what do you see in access_log - 500, 502, etc ?<br>
> > > ><br>
> > > > > Thanks for your help<br>
> > > > ><br>
> > > > > On Mon, Mar 10, 2008 at 10:02 AM, Igor Sysoev <<a href="mailto:is@rambler-co.ru" target="_blank">is@rambler-co.ru</a>><br>
> wrote:<br>
> > > > ><br>
> > > > > > On Mon, Mar 10, 2008 at 09:55:23AM -0400, James Golick wrote:<br>
> > > > > ><br>
> > > > > > > Nginx will always log an error when there's a 500?<br>
> > > > > ><br>
> > > > > > Yes, at least I have tried to log them all. The log is single way<br>
> > > > > > to know about the problems.<br>
> > > > > ><br>
> > > > > > So what do you see - 500, 502, 503, or 504 ?<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > --<br>
> > > > > > Igor Sysoev<br>
> > > > > > <a href="http://sysoev.ru/en/" target="_blank">http://sysoev.ru/en/</a><br>
> > > > > ><br>
> > > > > ><br>
> > > ><br>
> > > > --<br>
> > > > Igor Sysoev<br>
> > > > <a href="http://sysoev.ru/en/" target="_blank">http://sysoev.ru/en/</a><br>
> > > ><br>
> > > ><br>
> ><br>
> > --<br>
> ><br>
> ><br>
> ><br>
> > Igor Sysoev<br>
> > <a href="http://sysoev.ru/en/" target="_blank">http://sysoev.ru/en/</a><br>
> ><br>
> ><br>
<br>
</div></div></blockquote></div><br>