110556 2005-10-26 08:57 0000 apache2: clean shutdown patch 2008-03-24 00:28:26 0000 1 1 1 Unclassified Gentoo Linux Server unspecified All Linux RESOLVED FIXED P2 major --- 1 alchemyx@uznam.net.pl apache-bugs@gentoo.org aksansai@gmail.com anakin.skyw@gmx.de birder@ozemail.com.au john.mcfarlane@rockfloat.com kai@kaishome.de mail@patrick-nagel.net mattsch@gmail.com nospam@dolney.com peter@kerwien.homeip.net polynomial-c@gentoo.org alchemyx@uznam.net.pl 2005-10-26 08:57:03 0000 We should apply same patch as for squid, because often apache doesn't stop immediately. Proposed patch attached. alchemyx@uznam.net.pl 2005-10-26 08:58:07 0000 Created an attachment (id=71512) apache2 clean shutdown patch pquerna@apache.org 2005-10-26 10:08:04 0000 why? It does stop. The real solution is to either from backport or use 2.1, which has the graceful-stop feature. alchemyx@uznam.net.pl 2005-10-26 10:38:12 0000 On loaded servers when you issue /etc/init.d/apache stop it takes at least 5 to 10 seconds before every process dissapears (I am using mpm-worker if it gives any hint). Adding that solved problem, especialy when running apache restart, which always failed because of not-yet-dead processes of apache. I think it is clean and good solution, it does no harm for anybody not needing that feature. peter@kerwien.homeip.net 2006-05-02 12:01:40 0000 I would also like to see that something was done to the restart problem of apache. Often a restart fails, and you need to do a start after the failed restart. jakub@gentoo.org 2006-08-30 06:58:25 0000 *** Bug 145596 has been marked as a duplicate of this bug. *** kai@kaishome.de 2006-09-01 08:51:58 0000 (In reply to comment #2) > why? It does stop. > > The real solution is to either from backport or use 2.1, which has the > graceful-stop feature. Why? Yes, it does stop, but it does not immediatly restart - because it does not immediatly stop. I ask myself why you are argumenting against a quickfix. As far as I can see your argumentation is now almost 1 year old, I suggestion of backporting was not picked up. But apache2 is marked stable. Either the quickfix should be applied and a new bug should be opened for improving this - or apache 2.0 should be put back to testing or unstable. It is currently unusable in a production environment when you do automated restarts because it is totally unreliable. Sorry, just my 2 pence. I love Gentoo for it's stability and affords to keep packages stable with custom patches applied by the ebuilds (and 2.1 isn't marked stable). This argumentation is just ignorance. "The right way" is subject to your liking, not to the community's a/o users' liking. vericgar@gentoo.org 2006-10-15 16:12:24 0000 We have moved to using start-stop-daemon in apache 2.0.59-r1. start-stop-daemon should do all the heavy lifting for us, and so stops and restarts now work correctly. jakub@gentoo.org 2007-01-22 07:24:55 0000 *** Bug 163162 has been marked as a duplicate of this bug. *** jakub@gentoo.org 2007-01-31 17:30:10 0000 *** Bug 164717 has been marked as a duplicate of this bug. *** anakin.skyw@gmx.de 2007-01-31 23:59:47 0000 >and so stops and restarts now work correctly. Apparently not. Bug 164717 jakub@gentoo.org 2007-02-05 14:31:11 0000 *** Bug 165448 has been marked as a duplicate of this bug. *** jakub@gentoo.org 2007-02-05 14:31:29 0000 People are still moaning about this... Reopen. john.mcfarlane@rockfloat.com 2007-02-05 14:38:44 0000 Sorry for the dup... I should have thought to search closed bugs too? ziapannocchia@gmail.com 2007-04-09 07:28:38 0000 I had a lot of problems with apache-2.2.4 stop and restart functions. 1. start-stop-daemon does not work, while apache2ctl does. This behaviour is undependent from the following observations. 2. http.conf does explicitly not use "PidFile" voice and defaults to /var/run/apache2.pid. I thing may be better to add an explicit line for it. 3. init script uses explicitly the option "--pidfile" setted to /var/run/apache2.pid. I thing may it be better to insert a variable in /etc/conf/apache to change this choice. phreak@gentoo.org 2007-05-26 18:20:47 0000 This should be fixed now. jakub@gentoo.org 2008-01-20 09:16:14 0000 *** Bug 206730 has been marked as a duplicate of this bug. *** jakub@gentoo.org 2008-02-15 19:29:35 0000 *** Bug 210272 has been marked as a duplicate of this bug. *** mattsch@gmail.com 2008-02-15 19:37:43 0000 (In reply to comment #15) > This should be fixed now. > How exactly has this been fixed? Is there a patch/version we can test? jakub@gentoo.org 2008-02-15 19:39:37 0000 (In reply to comment #18) > How exactly has this been fixed? Is there a patch/version we can test? No, there's no fix if you still have the issue. Providing a wrong return status is none of Gentoo problem, take it upstream. mattsch@gmail.com 2008-02-15 19:42:52 0000 Has anyone filed a bug for this upstream yet? mattsch@gmail.com 2008-02-15 20:06:18 0000 Since I could not find a bug reported on this upstream, I filed one myself there. Here's a link to the bug if you want to track it: http://issues.apache.org/bugzilla/show_bug.cgi?id=44433 jakub@gentoo.org 2008-02-28 05:05:37 0000 *** Bug 211690 has been marked as a duplicate of this bug. *** jakub@gentoo.org 2008-02-28 06:17:36 0000 Since people keep adding themselves here: you do NOT want to use restart, pretty much ever. Use /etc/init.d/apache2 reload if all you are after is reloading your configuration. You can configure how the reload will be done via RELOAD_TYPE variable in /etc/conf.d/apache2 (most likely you just want to stick with the default graceful one). For more info, see http://httpd.apache.org/docs/2.2/stopping.html If you want /etc/init.d/restart to work as with all the rest of the stuff out there, make upstream fix it - http://issues.apache.org/bugzilla/show_bug.cgi?id=44433 - since restart really means stop && start and the second part won't happen until the first one succeeded; alas apache doesn't bother itself with checking properly whether it really stopped first, and just returns success. hollow@gentoo.org 2008-02-28 16:28:29 0000 the reason we don't actually fix (read: workaround) this, can be easily seen at http://svn.debian.org/viewsvn/pkg-apache/trunk/apache2/apache2.2-common.apache2.init?rev=544&view=markup such crap is just not maintainable hollow@gentoo.org 2008-03-22 15:33:48 0000 i have to specify a comment hollow@gentoo.org 2008-03-22 15:34:32 0000 fixed in svn with much less code mattsch@gmail.com 2008-03-23 17:52:45 0000 I thought the whole point was that this was a bug the developers at apache needed to fix? hollow@gentoo.org 2008-03-24 00:28:26 0000 (In reply to comment #27) > I thought the whole point was that this was a bug the developers at apache > needed to fix? > yes, but i decided we cannot wait until upstream fixes their signal mess, i tried it, but gave up after two hours or so ... 71512 2005-10-26 08:58 0000 apache2 clean shutdown patch apache2-cleanshutdown.patch text/plain LS0tIC90bXAvYXBhY2hlMgkyMDA1LTEwLTI2IDE3OjU2OjM1LjAwMDAwMDAwMCArMDIwMAorKysg L2V0Yy9pbml0LmQvYXBhY2hlMgkyMDA1LTEwLTI2IDE3OjUzOjA4LjAwMDAwMDAwMCArMDIwMApA QCAtODMsNiArODMsMzMgQEAKIAljaGVja2NvbmZpZyB8fCByZXR1cm4gMQogCWViZWdpbiAiU3Rv cHBpbmcgYXBhY2hlMiIKIAkke0FQQUNIRTJ9ICR7QVBBQ0hFMl9PUFRTfSAtayBzdG9wCisKKwlQ SUQ9YGNhdCAvdmFyL3J1bi9hcGFjaGUyLnBpZCAyPi9kZXYvbnVsbGAKKworICAgICAgICAjIE5v dyB3ZSBoYXZlIHRvIHdhaXQgdW50aWwgc3F1aWQgaGFzIF9yZWFsbHlfIHN0b3BwZWQuCisgICAg ICAgIHNsZWVwIDIKKyAgICAgICAgaWYgdGVzdCAtbiAiJFBJRCIgJiYga2lsbCAtMCAkUElEIDI+ L2Rldi9udWxsCisgICAgICAgIHRoZW4KKyAgICAgICAgICAgICAgICBlaW5mb24gIldhaXRpbmcg LiIKKyAgICAgICAgICAgICAgICBjbnQ9MAorICAgICAgICAgICAgICAgIHdoaWxlIGtpbGwgLTAg JFBJRCAyPi9kZXYvbnVsbAorICAgICAgICAgICAgICAgIGRvCisgICAgICAgICAgICAgICAgICAg ICAgICBjbnQ9YGV4cHIgJGNudCArIDFgCisgICAgICAgICAgICAgICAgICAgICAgICBpZiBbICRj bnQgLWd0IDYwIF0KKyAgICAgICAgICAgICAgICAgICAgICAgIHRoZW4KKyAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgIyBXYWl0ZWQgMTIwIHNlY29uZHMgbm93LiBGYWlsLgorICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICBlZW5kIDEgIkZhaWxlZC4iCisgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgIGJyZWFrCisgICAgICAgICAgICAgICAgICAgICAgICBmaQorICAg ICAgICAgICAgICAgICAgICAgICAgc2xlZXAgMgorICAgICAgICAgICAgICAgICAgICAgICAgZWNo byAtbiAiLiIKKyAgICAgICAgICAgICAgICBkb25lCisgICAgICAgICAgICAgICAgZWNobyAtbiAi ZG9uZS4iCisgICAgICAgICAgICAgICAgZWVuZCAwCisgICAgICAgIGVsc2UKKyAgICAgICAgICAg ICAgICBlZW5kIDAKKyAgICAgICAgZmkKKwogCWVlbmQgJD8KIH0KIAo=