On Wed, 12 Apr 2000, Bill Moseley wrote:
> Hello,
>
> I noticed on the Apache server-status report a child that is stuck in "G"
> (Gracefully finishing) after a SIGUSR1 today. Twelve hours ago.
>
> I don't have root access on this machine, but I thought I'd run a CGI
> script to run as "nobody" and kill off the child. (I've done this once
> before when working late from home and sending a mod_perl script into a
> memory hungry loop.)
>
> But in this case the child sitting there in "G" just won't die. I've tried
> sending as many signals as I can imagine HUP INT QUIT ABRT KILL TERM USR1
> STOP CONT and THAW. I did note that the process was serving it's very
> first request when SIGURS1 was sent. And I just sent a SIGHUP to another
> Apache child from a CGI script and the child died.
>
> We had a similar situation a month or so back where an Apache restart left
> a bunch of children behind (and holding onto port 80), and thus the server
> wouldn't restart. This time running as root and still couldn't kill the
> processes. The machine was finally rebooted.
>
> Anyone know how to kill off these children (without having to reboot)?
Looks like a system problem, what do you see when you attach to a process
with 'strace -p PID'? For example it might enter some uninterruptable
sleep waiting for some event to happen, but this will never do. Generally
using strace (or truss) reveals some info.
> % uname -a
> SunOS 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-Enterprise
>
> Apache/1.3.9 (Unix) mod_perl/1.21
>
> Thanks,
>
> Bill Moseley
> mailto:[EMAIL PROTECTED]
>
______________________________________________________________________
Stas Bekman | JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ | mod_perl Guide http://perl.apache.org/guide/
mailto:[EMAIL PROTECTED] | http://perl.org http://stason.org/TULARC/
http://singlesheaven.com| http://perlmonth.com http://sourcegarden.org
----------------------------------------------------------------------
