Michael B Allen wrote:
I have a customer who very occasionally sees apache workers hang. I'm
pretty sure this is caused by an errant module but I don't know which
one.
Is there any way to determine which module is causing Apache workers to hang?
Can I temporarily disable that SIGTERM so that I
On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis j...@joe-lewis.com wrote:
Michael B Allen wrote:
I have a customer who very occasionally sees apache workers hang. I'm
pretty sure this is caused by an errant module but I don't know which
one.
Is there any way to determine which module is causing
Michael B Allen wrote:
On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis j...@joe-lewis.com wrote:
Michael B Allen wrote:
I have a customer who very occasionally sees apache workers hang. I'm
pretty sure this is caused by an errant module but I don't know which
one.
Is there any way to
Michael B Allen wrote:
On Fri, Oct 16, 2009 at 2:42 PM, Joe Lewis j...@joe-lewis.com wrote:
Michael B Allen wrote:
On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis j...@joe-lewis.com wrote:
Michael B Allen wrote:
I have a customer who very occasionally sees apache workers
Michael B Allen wrote:
Can I temporarily disable that SIGTERM so that I can have enough time
to attach GDB to the hanging processes?
Mike,
The code which sends the SIGTERM is in mpm_common.c:
static int reclaim_one_pid(pid_t pid, action_t action)
{
...
case SEND_SIGTERM:
/* ok, now
On Fri, Oct 16, 2009 at 8:04 PM, Chris Kukuchka chr...@sequoiagroup.com wrote:
Michael B Allen wrote:
Can I temporarily disable that SIGTERM so that I can have enough time
to attach GDB to the hanging processes?
Mike,
The code which sends the SIGTERM is in mpm_common.c:
static int
