[Mongrel] Spinning mongrels and SIGUSR1

Zed Shaw zedshaw at zedshaw.com
Wed Sep 20 22:22:26 EDT 2006


On Wed, 2006-09-20 at 18:26 -0400, Ian C. Blenke wrote:
> First off: Our clusters are LVS balanced Apache 2.2.3 + 
> mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + 
> memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a 
> pgcluster backend.
> 
> On 2 of our deployed clusters, we are getting the "spinning mongrel" 
> problem. As the clusters are very low volume right now, it takes days to 
> collect a spinner, making it difficult to debug what the problem might be.
> 
>  From what I've been following on the list, the appropriate next 
> debugging step is to send a SIGUSR1 signal to the spinning mongrel to 
> get it to spit out what it thinks it is currently running.

USR2 is the debugging signal.  You actually want to turn it on a few
minutes after they start, and it's safe to turn on in production (not
much of a performance hit).


-- 
Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu
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