On Thu, Mar 28, 2019 at 11:18 PM Eric Covener wrote:
>
> > There is a possibility. If you are using MPM and have set a non-zero
> > value for MaxConnectionsPerChild, this can happen. Once
> > MaxConnectionsPerChild limit is reached, that child server will be
> > terminated and a new one will be
> There is a possibility. If you are using MPM and have set a non-zero
> value for MaxConnectionsPerChild, this can happen. Once
> MaxConnectionsPerChild limit is reached, that child server will be
> terminated and a new one will be started. Do you have that in your
> config?
If there's a
John,
On Thu, Mar 28, 2019 at 1:23 AM Rose, John B wrote:
>
> As always, a "thank you" to everyone that works on Apache.
>
>
> Some background and resultant question ...
>
>
> We had made some changes in the afternoon to some virtual host configs that
> we intended to implement the next morning
Eric, as always, thanks for replying.
I think logrotate is the likely culprit.
Looking at apachectl status it doesn’t do a stop start, since no indication of
an overnight restart. So I assume a “graceful” on Linux
Thanks again for the help
Sent from my iPad
On Mar 27, 2019, at 5:21 PM, Eric
> Does Apache do a "graceful" restart automatically over time?
No. Some likely culprits: logrotate (not to be confused with
rotatelogs) or third-party control panels that manage your webserver
config. Or an unplanned reboot which would not really be a graceful
restart but a stop/start.
As always, a "thank you" to everyone that works on Apache.
Some background and resultant question ...
We had made some changes in the afternoon to some virtual host configs that we
intended to implement the next morning with a graceful restart of Apache.
That was going to be coordinated
