My mongrel cluster seems to have some weird issues. Anyone here with
some insight into whats going on?
Tue Jan 13 09:36:34 -0800 2009: Reaping 7 threads for slow workers
because of 'shutdown'
Thread #Thread:0x2bb8adc8 sleep is too old, killing.
Tue Jan 13 09:36:34 -0800 2009: Error calling
Recommended: http://www.informit.com/store/product.aspx?isbn=0321544684
Specifically sections 3 and 4, on lsof and strace, the latter of which
should be informative re: what the threads are doing when they're not
responding to a shutdown, provided you can catch one in the act.
Does this happen
This is otherwise stock mongrel behaviour; it's just trying to comply
with
a
shutdown request, and will forcibly kill threads that are unresponsive.
Yup, you have one active request that is blocked on something (most likely
the db, or a web services call). The standard mogrel shutdown
I would have expected you to be getting the following on load:
c:/ruby/lib/ruby/gems/1.8/gems/daemons-1.0.9/lib/daemons/daemonize.rb:103:in
`fork': fork() function is unimplemented on this machine (NotImplementedError)
The -d is not actually supported on Windows, thus the warning:
** WARNING:
Hi,
thank you for your help.
I didn't patch anything.
There isn't much load on the server. Its something about a call to a label,
every 20 or 30 seconds. Threre is enough Ram, that's not the problem. Cpu
power is enough. I simply don't know why it stops working.
In an older Mongrel version the
Incidentally that no method error 'w' is already fixed in trunk; we
need some more test coverage of an unrelated change before we can make
a release though.
Evan
On Nov 21, 2007 7:33 AM, Oliver Schneider [EMAIL PROTECTED] wrote:
Hi,
thank you for your help.
I didn't patch anything.
There
