As I reported in bug #220220, on my system the problem is worse:
When apache kills some of it's children (too many idle processes,
MaxRequestsPerChild reached) it also gets stuck in Gracefully
finishing state.
This leaves from time to time stuck child processes, that remain there
till apache
*** This bug is a duplicate of bug 174805 ***
https://bugs.launchpad.net/bugs/174805
The reload problem is reported on Ubuntu bug #174805
** Changed in: apache2 (Ubuntu)
Sourcepackagename: apache = apache2
** Changed in: apache2 (Ubuntu)
Status: New = Invalid
** This bug has been
On a devel machine (under light load compared to production servers) the
reload does not give any problem with hardy.
--
[gutsy] graceful-stop fails when apache listens on more than one socket
https://bugs.launchpad.net/bugs/174805
You received this bug notification because you are a member of
Please, reopen this bug. It's still affecting gutsy.
It shouldn't be hard to backport this change. Currently gutsy is
unusable as a webserver in production evironments, and upgrade to hardy
is usually a hard task it must be handle with a lot of care. This is a
must fix!
--
[gutsy] graceful-stop
Sadly there is not fix :(. Avoid apache reload, use stop; sleep 5;
start.
--
[gutsy] graceful-stop fails when apache listens on more than one socket
https://bugs.launchpad.net/bugs/174805
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
