Thanks for the reply, Ezra.<br><br>Everything looks kosher there, too. However, the problem is now solved - we moved to thin! :)<br><br>J.<br><br><div class="gmail_quote">On Mon, Mar 10, 2008 at 3:03 PM, Ezra Zygmuntowicz <<a href="mailto:ezmobius@gmail.com">ezmobius@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>
Please double count the number of mongrels you have running and the<br>
ports they run on and then doublecheck the upstream block in your<br>
nginx.conf to make sure it matches exactly. Also restart all of your<br>
mongrels so they are fresh.<br>
<br>
We usually see this error when the number of running mongrels is<br>
changed without updating the number of servers in the upstream block.<br>
<br>
Cheers-<br>
-Ezra<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
On Mar 11, 2008, at 10:34 AM, Aníbal Rojas wrote:<br>
<br>
> 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>
> Aníbal<br>
><br>
> On Tue, Mar 11, 2008 at 10:08 AM, James Golick<br>
> <<a href="mailto:jamesgolick@gmail.com">jamesgolick@gmail.com</a>> wrote:<br>
>> Still says 200. Somebody is throwing this error and won't admit to<br>
>> 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">is@rambler-co.ru</a>><br>
>> 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<br>
>>>> 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">is@rambler-co.ru</a>><br>
>>>> 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">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<br>
>>>>>>> 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>
<br>
</div></div><font color="#888888">- Ezra Zygmuntowicz<br>
-- Founder & Software Architect<br>
-- <a href="mailto:ezra@engineyard.com">ezra@engineyard.com</a><br>
-- EngineYard.com<br>
<br>
<br>
</font></blockquote></div><br>