Date: Wed, 8 Jun 2005 10:42:02 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Jiawei Ye <leafy7382@gmail.com> Cc: Peter Jeremy <PeterJeremy@optushome.com.au>, freebsd-current@freebsd.org Subject: Re: unkillable apache httpd process Message-ID: <20050608154202.GH59028@dan.emsphone.com> In-Reply-To: <c21e92e2050608083621597917@mail.gmail.com> References: <c21e92e205060800524f9d7e89@mail.gmail.com> <20050608091603.GG39114@cirb503493.alcatel.com.au> <c21e92e20506080223235a7364@mail.gmail.com> <20050608152610.GG59028@dan.emsphone.com> <c21e92e2050608083621597917@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 08), Jiawei Ye said: > On 6/8/05, Dan Nelson <dnelson@allantgroup.com> wrote: > > If it's consuming CPU it should be killable. Tried kill -9? If it's > > really threaded, "ps lHp 3794" will print what each kernel thread is > > doing; maybe only one thread is hung. > > kill -9 solves the problem. But the apache2.sh in /usr/local/rc.d > cannot restart it properly. > > root@orion:/home/leafy# /usr/local/etc/rc.d/apache2.sh restart > Performing sanity check on apache2 configuration: > Syntax OK > Stopping apache2. > Waiting for PIDS: 5696, 5696, 5696, 5696, 5696, 5696, 5696, 5696, > 5696, 5696, 5696, 5696, 5696, 5696, 5696, 5696 > it goes on..... > Also, the unkillable has only 1 thread as shown in the top output. rc.d scripts just send a SIGTERM to the process by default. If apache has blocked that signal, there's not much the script can do. What you could do is edit apache2.sh and add a line saying "sig_stop=-KILL", which will make the shutdown action send a SIGKILL (aka -9) signal to apache. This won't be a clean shutdown, though. Better to try and debug apache and find out what it's doing. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050608154202.GH59028>