Hi,
I think I'm affected by the same problem.
After upgrading to 2.4.33-3 it's happening consistently after every
reload, to all the workers (making all the requests to the server time
out until I restart the server).
I've been juggling between one of the older versions (2.4.25-3) and the
curren
We now have a temporary work around which run apachectl and kills the
processes stuck in the "Gracefully stopping" state.
This is then cron'd to run after logrotate.
--
Dogsbody Technology Ltd : http://www.dogsbodytechnology.com/
Dogsbody Hosting : http://www.dogsbodyhosting.net/
Hello,
No this is not a new bug. We have been investigating this since January.
Rob (Dan's colleague).
On April 05, 2018 08:18 Stefan Fritsch wrote:
Hi Dan,
Hi Dan,
On Wed, 4 Apr 2018, Dan Benton wrote:
> Package: apache2
> Version: 2.4.10-10+deb8u12
> Severity: normal
Is this a new issue with version 2.4.10-10+deb8u12 (from the security
update a few days ago) or have you also observed it with the previous
version 2.4.10-10+deb8u11?
Cheers,
Stefa
Package: apache2
Version: 2.4.10-10+deb8u12
Severity: normal
Dear Maintainer,
I am finding some Apache processes stuck in a gracefully finishing state after
an Apache reload. The only way to clear these processes down is to restart
Apache or killing the individual processes.
The way these proce
5 matches
Mail list logo