DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40514>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40514

           Summary: would like GracefulShutdownTimeout to work for graceful
                    restarts too
           Product: Apache httpd-2
           Version: 2.2.2
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: All
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Running 2.2.3 here on RHEL 3.  We use cgiwrap (a suexec clone, see
cgiwrap.sf.net) (due to historical reasons) to run user cgi programs (via
mod_cgi in prefork mode).  Nightly we have a cron job that uses 'apachectl
graceful' to restart things so logs can be rotated.  I've noticed that if a
user's script hangs for some reason (i.e. no CPU time is being used) that after
5 minutes or so apache will complain about the CGI request timing out and then
the httpd child that spawned the CGI will enter the C state.  When the
'apachectl graceful' is issued then that httpd child will enter the G state and
stay around in that state perpetually.  What I would like is for something like
GracefulShutdownTimeout to apply to graceful restarts and not just graceful
stops so that after a configured amount of time apache would start forcefully
killing these hung httpd children.

Here's an example cgi that can be used to see this problem:

#!/usr/local/bin/php

<?php

while (1) {
        $i = 1;
        sleep(500);
}
?>

Just run that, wait until apache reports the CGI timed out and it has entered
the C state.  Then do a graceful restart upon which it will enter the G state
and keep running.  I've verified this also happens when running the CGI via 
suexec.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to