The following reply was made to PR os-irix/2002; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Jason Priebe <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: os-irix/2002: unkillable httpd processes Date: Thu, 26 Mar 1998 10:52:07 -0700 (MST) Did you try adding a "LockFile /tmp/accept.lock" or something along those lines to your Configuration file? You must not have it on a NFS mounted disk. On 26 Mar 1998, Jason Priebe wrote: > > >Number: 2002 > >Category: os-irix > >Synopsis: unkillable httpd processes > >Confidential: no > >Severity: critical > >Priority: medium > >Responsible: apache > >State: open > >Class: sw-bug > >Submitter-Id: apache > >Arrival-Date: Thu Mar 26 09:10:00 PST 1998 > >Last-Modified: > >Originator: [EMAIL PROTECTED] > >Organization: > apache > >Release: 1.2.5 > >Environment: > IRIX barkley 6.2 03131015 IP22 > gcc version 2.7.2.3 (running on another machine under IRIX 5.3) > >Description: > To restart our httpd, we use > > kill -HUP `cat /usr/local/etc/httpd/logs/httpd.pid` > > Most of the time, this successfully restarts the web server, allowing us > to rotate our logs. But sometimes the server shuts down leaving a few > httpd processes that are unkillable. (they refuse to respond to "kill -9"). > The only recourse at that point is a reboot. > > We have also seen similar behavior when stopping the web server, using: > > kill `cat /usr/local/etc/httpd/logs/httpd.pid` > > Some of the processes hang inexplicably. The server root is on an > NFS-mounted volume, if that is of any help. > >How-To-Repeat: > > >Fix: > n > >Audit-Trail: > >Unformatted: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > > >
