[Mongrel] mongrel proxies waiting endlessly

Zed Shaw zedshaw at zedshaw.com
Mon Sep 4 19:39:31 EDT 2006


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.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.



More information about the Mongrel-users mailing list