Nothing. There's nothing in the logs.<br><br>According to the mongrel mailing list, it can raise 500s when it's in err state. But, does it respond with an incorrect error code? I dunno.<br><br>I mean, I'm not seeing anything in any error logs, and nginx is reporting a 200 for all requests. wtf?<br>
<br><div class="gmail_quote">On Mon, Mar 10, 2008 at 10:17 AM, Aníbal Rojas <<a href="mailto:anibalrojas@gmail.com">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;">
But what does the production.log or mongrel logs say?<br>
<br>
I mean, can you find errors in the backend logs matching the date/time<br>
for the errors in the nginx log?<br>
<font color="#888888"><br>
--<br>
Aníbal Rojas<br>
<a href="http://hasmanydevelopers.com" target="_blank">http://hasmanydevelopers.com</a><br>
<a href="http://rubycorner.com" target="_blank">http://rubycorner.com</a><br>
<a href="http://anibal.rojas.com" target="_blank">http://anibal.rojas.com</a><br>
</font><div><div></div><div class="Wj3C7c"><br>
On Tue, Mar 11, 2008 at 9:17 AM, James Golick <<a href="mailto:jamesgolick@gmail.com">jamesgolick@gmail.com</a>> wrote:<br>
> Nothing... all of the mongrels respond normally when hit without nginx.<br>
><br>
> This has got to be an nginx issue...<br>
><br>
><br>
><br>
> On Mon, Mar 10, 2008 at 9:40 AM, James Golick <<a href="mailto:jamesgolick@gmail.com">jamesgolick@gmail.com</a>> wrote:<br>
><br>
> > Yeah, I don't think it's mongrel, as they're all started the identical way<br>
> (thru a process monitor).<br>
> ><br>
> > Also, every time I get the error, I see one of those issues in the nginx<br>
> error.log. But, I guess it still could be happening upstream....<br>
> ><br>
> > I will test them all and report back.<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Mon, Mar 10, 2008 at 9:29 AM, Phillip B Oldham<br>
> <<a href="mailto:phill@theactivitypeople.co.uk">phill@theactivitypeople.co.uk</a>> wrote:<br>
> ><br>
> > ><br>
> > > I was seeing something similar with PHP5 fastcgi and lighttpd, though it<br>
> was a lot more than 10% - maybe 25-50. I'm getting a little worried as I<br>
> think I may be seeing the same thing at around 5-10% with nginx.<br>
> > ><br>
> > > During my investigations into why this was happening in lighttpd, I came<br>
> across the following paragraph in the mod_fcgi docs:<br>
> > ><br>
> > > Adds a MaxRequestsPerProcess parameter that allows mod_fcgid to exit<br>
> after handling a certain number of requests, similar to the existing<br>
> ProcessLifeTime option.<br>
> > ><br>
> > > This solves a problem with PHP in FastCGI mode. By default, PHP stops<br>
> accepting new FastCGI connections after handling 500 requests;<br>
> unfortunately, there is a potential race condition during the PHP cleanup<br>
> code in which PHP can be shutting down but still have the socket open, so<br>
> mod_fcgid under heavy load can send request number 501 to PHP and have it<br>
> "accepted", but then PHP appears to simply exit, causing errors. Not too<br>
> sure if your rails app/mongrel is restarting processes after a set limit and<br>
> coming across the same race condition?<br>
> > ><br>
> > > If this problem is could become aparent in nginx it would be great if<br>
> there was a plugin to spawn and manage fcgi threads which could limit the<br>
> number of connections to each backend.<br>
> > ><br>
> > > HTH.<br>
> > > Phill<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > James Golick wrote:<br>
> > > I have nginx running as a proxy to about twelve upstream app servers,<br>
> serving a rails app. Nothing else really in this configuration.<br>
> > ><br>
> > > I am seeing about 10% of requests throwing 500 errors, and this in my<br>
> error log:<br>
> > ><br>
> > > 2008/03/10 08:41:05 [info] 6632#0: *12005 client closed prematurely<br>
> connection while sending response to client, client: xxx, server: xxx,<br>
> request: xxx, host: xxx, referrer: xxx<br>
> > ><br>
> > > I'm also seeing lots of:<br>
> > ><br>
> > > client xxx closed keepalive connection<br>
> > ><br>
> > > but that strikes me as normal, and I'm seeing:<br>
> > ><br>
> > > client closed prematurely connection while reading client request line,<br>
> client: xxx, server: xxx<br>
> > ><br>
> > > I have googled far and wide, and the best answers I came up with were to<br>
> add these lines to my conf:<br>
> > ><br>
> > > proxy_ignore_client_abort on;<br>
> > > proxy_next_upstream error;<br>
> > ><br>
> > > but, that doesn't seem to have solved the problem.<br>
> > ><br>
> > > Any ideas?<br>
> > ><br>
> > > Thanks in advance.<br>
> > ><br>
> > ><br>
> > > --<br>
> > ><br>
> > ><br>
> > ><br>
> > > Phillip B Oldham<br>
> > > The Activity People<br>
> > > <a href="mailto:phill@theactivitypeople.co.uk">phill@theactivitypeople.co.uk</a> ________________________________<br>
><br>
> > ><br>
> > > Policies<br>
> > ><br>
> > > This e-mail and its attachments are intended for the above named<br>
> recipient(s) only and may be confidential. If they have come to you in<br>
> error, please reply to this e-mail and highlight the error. No action should<br>
> be taken regarding content, nor must you copy or show them to anyone.<br>
> > ><br>
> > > This e-mail has been created in the knowledge that Internet e-mail is<br>
> not a 100% secure communications medium, and we have taken steps to ensure<br>
> that this e-mail and attachments are free from any virus. We must advise<br>
> that in keeping with good computing practice the recipient should ensure<br>
> they are completely virus free, and that you understand and observe the lack<br>
> of security when e-mailing us. ________________________________<br>
><br>
> ><br>
> ><br>
<br>
</div></div></blockquote></div><br>