For some time now, I run into the following problem: # /etc/init.d/apache2 restart * Stopping apache2 ... [ ok ] * Starting apache2 ... httpd (pid 17167) already running [ ok ] The init script says 'ok', but afterwards apache is actually NOT running. When running the init script again, you get: # /etc/init.d/apache2 restart * Stopping apache2 ... httpd (no pid file) not running [ ok ] * Starting apache2 ... [ ok ] This is far from optimal and should be fixed. Reproducible: Always Steps to Reproduce: 1. /etc/init.d/apache2 restart Actual Results: Apache stops, but doesn't get started again, although the init script claims everything worked ok. Expected Results: Apache restarts.
Created attachment 144808 [details, diff] Adds a 'check-if-really-stopped' loop into the stop() function of the apache2 init script I'm sure this could be done better... but as roothorick@#gentoo said: "a quick fix now and an optimal solution later is better than merely an optimal solution later" ;)
Nope, not going to happen. *** This bug has been marked as a duplicate of bug 110556 ***
(In reply to comment #2) > Nope, not going to happen. > > *** This bug has been marked as a duplicate of bug 110556 *** > Thanks for the lesson: We don't want to have workarounds that make buggy software usable. Instead we let everybody write their own workaround and give unhelpful comments to people who suggest a feasible solution in public. Good that I know that now, so I can adjust my behaviour and be as unhelpful as possible.
The above patch doesn't solve anything, while potentially causing serious issues like being completely unable to do reboot a box gracefully due to infinite stop loop. As noted on the original bug, get apache fixed properly upstream.
(In reply to comment #4) > The above patch doesn't solve anything, while potentially causing serious > issues like being completely unable to do reboot a box gracefully due to > infinite stop loop. Ridiculous. Calling '/etc/init.d/apache2 restart' will result in having apache2 not running at all afterwards - is that your idea of something working 'gracefully'? > As noted on the original bug, get apache fixed properly upstream. I totally agree. But as has been written before: "a quick fix now and an optimal solution later is better than merely an optimal solution later". And PLEASE oh PLEASE spare the "it's not our responsibility" crap.
We are not interested in hacks; sorry. Since this apparently won't go anywhere in a productive way, please note that this bug is a duplicate and CLOSED.
