On Tue, 24 Oct 2006 13:27:01 -0700 Michael Moen <[EMAIL PROTECTED]> wrote:
> On Oct 24, 2006, at 3:10 PM, Zed A. Shaw wrote: > > Go grab the 0.3.13.5 pre-release and run it under USR1 debugging in > > production. It's got a tweak to the debugging output so that you > > can better understand what action is blocking the mongrel. > > Something like this: > > > > $ gem install mongrel --source=http://mongrel.rubyforge.org/releases > > $ <start mongrel_rails however you do> > > $ killall -USR1 mongrel_rails > > > > Then, you're looking for lines in mongrel.log: > > > > Tue Oct 24 15:07:07 PDT 2006: 0 threads sync_waiting for /test, 1 > > still active > > in Mongrel. > > Here's a handful of the ones we logged yesterday, as you can see it > wasn't in a happy state. I'll run off and grab the pre-release for > one of the boxes and give it another spin. Is this with the 0.3.13.5 pre-release? It looks like you don't have the change that makes it clearer what is blocking (or that it's not really working well). -- 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. _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
