Re: Apache graceful-stop

[Paul Silevitch <paul@xxxxxxxxxxxxx>]

I am seeing this behavior too.

If I do a graceful-stop followed by a start on a system that I know is getting no traffic, the old parent process sometimes hangs around for a bit (I think for GracefulShutdownTimeout secs).

On a related note - If I do a graceful-stop followed by a start on a heavily loaded system, the start sometimes doesn't successfully complete and returns a "httpd (pid xxx) already running".  Has anyone else seen this?  Any ideas on why this happens?

Thanks,

Paul

>I stopped load and waited for thrice as long as our application timeout.

>

>On Thu, Aug 20, 2009 at 7:43 AM, Eric Covener<covener@xxxxxxxxx> wrote:

> On Thu, Aug 20, 2009 at 10:24 AM, Mohit Anchlia<mohitanchlia@xxxxxxxxx> wrote:

>> I think I knew that. Question is even though there were no outstanding

>> requests the httpd servers stayed there until I finally killed them

>

> How did you ensure that there were no outstanding requests?

>

> --

> Eric Covener

> covener@xxxxxxxxx

>

> ---------------------------------------------------------------------

> The official User-To-User support forum of the Apache HTTP Server Project.

> See <URL:http://httpd.apache.org/userslist.html> for more info.

> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx

>   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx

> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx

>

>

---------------------------------------------------------------------

The official User-To-User support forum of the Apache HTTP Server Project.

See <URL:http://httpd.apache.org/userslist.html> for more info.

To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx

   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx

For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx