[Mongrel] mongrel proxies waiting endlessly

hemant gethemant at gmail.com
Mon Sep 4 20:00:00 EDT 2006


On 9/5/06, Zed Shaw <zedshaw at zedshaw.com> wrote:
>
> On Tue, 2006-09-05 at 04:49 +0530, hemant wrote:
> > Sometime my mongrel server threads..would simply stop responding to
> > the requests...and in the logs i get following error:
> >
> > Tue Sep 05 03:56:40 IST 2006: ERROR: Transport endpoint is not
> > connected - getpeername(2)
> > Tue Sep 05 03:59:21 IST 2006: ERROR: Transport endpoint is not
> > connected - getpeername(2)
> > Tue Sep 05 03:59:21 IST 2006: ERROR: Transport endpoint is not
> > connected - getpeername(2)
> > Tue Sep 05 03:59:47 IST 2006: ERROR: Transport endpoint is not
> > connected - getpeername(2)
> > Tue Sep 05 03:59:47 IST 2006: ERROR: Transport endpoint is not
> > connected - getpeername(2)
>
> Make sure you have the latest 0.3.13.4 pre-release, run your code under
> it, and after mongrel starts, turn on USR1 debugging:
>
> killall -USR1 mongrel_rails
>
> Then, look for any logging messages in mongrel.log that say there's tons
> of threads waiting for one of your rails actions.  Go fix that rails
> action and you'll be set.
>

I was using killall -USR1, but in your recent post..i have seen that you
have updated the pre-release server...and hence i update the mongrel gem
and..i am debugging it again..

Tue Sep 05 05:03:32 IST 2006: 0 threads sync_waiting for
/images/tab_but_normal1.png, 4 still active in mongrel.

So, what does the above line mean? 4 still active in mongrel? does it mean
that 4 threads are waiting for this file?

Does it mean..that for every file that is not found...in the rails
application directory, mongrel threads wait?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060905/5be20117/attachment.html 


More information about the Mongrel-users mailing list