Bill Moseley <[EMAIL PROTECTED]> writes:
> Hello,
>
> I hope I'm not too far off topic. At least this is a mod_perl built server.
>
> One child will not die -- while restarting the server reported:
>
> [warn] child process 6379 still did not exit, sending a SIGTERM
> [error] child process 6379 still did not exit, sending a SIGKILL
> [error] could not make child process 6379 exit, attempting to continue anyway
> [notice] caught SIGTERM, shutting down
>
> Attempting to kill and kill -9 as su root failed to kill the process. Any
> ideas why the child won't die, or what could cause it to hang? The process
> has now been sitting there for an hour blocking any attempts to restart the
> server on the same port.
>
> Is it possible that a server process could hang if a socket was left in a
> CLOSE_WAIT state?
I have seen this before a few times. If you do a ps and look at the
status of the process, it's likely in "D" which stands for
uninterruptible sleep. At least, if this were linux it probably would
:)
Sounds like the process is waiting on the kernel. You may have to
down the server to get it back unless you can figure out what it is
waiting for.
Again, this is Linux advice, so it may or may not be applicable. But
maybe it will help you find the problem. Perhaps the 'lsof' command
will show you if it has a file open. Generally D means either a
kernel bug or hardware failure. Neither are particularly happy
occurances...
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
