Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Michael B Allen
On Fri, Oct 16, 2009 at 8:04 PM, Chris Kukuchka 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 reclaim_one_pi

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Chris Kukuchka
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 it's

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Joe Lewis
Michael B Allen wrote: On Fri, Oct 16, 2009 at 2:42 PM, Joe Lewis wrote: Michael B Allen wrote: On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis wrote: Michael B Allen wrote: I have a customer who very occasionally sees apache workers hang. I'm pretty sure this is caused

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Michael B Allen
On Fri, Oct 16, 2009 at 2:42 PM, Joe Lewis wrote: > Michael B Allen wrote: >> >> On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis 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 mod

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Joe Lewis
Michael B Allen wrote: On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis 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 i

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Michael B Allen
On Fri, Oct 16, 2009 at 1:10 PM, Joe Lewis 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 Apache

Re: Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Joe Lewis
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

Debugging: child process 14446 still did not exit, sending a SIGTERM

2009-10-16 Thread Michael B Allen
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 can have enough time to a