[Bug 1018171] [NEW] apache2 init script report start success too early

Nicola lists at svrinformatica.it
Tue Jun 26 22:36:51 UTC 2012


Public bug reported:

apache2 init script after executing apache2ctl start should check if
apache2 is really running before reporting success,

this is problematic for example if you use apache2 init script as lsb
resource in a pacemaker cluster:

1) apache2 init script report success on start
2) pacemaker monitor the resource and find that apache2 is not yet running and the cluster service fail
3) pacemaker try to restart apache, after some time the original started apache come up

adding a sleep of 5 seconds after apache2ctl start solve the problem and
pacemaker does not fail. If you take a look to the apache RA script you
will see that it monitor apache after starting it to make sure the web
server is really started before returning success

I know ubuntu devs probably don't care about this since they want
migrate init script to upstart, this bug report is to save time for
people who want to use apache2 init script as lsb resource in a
pacemaker cluster,

please note that apache2 init script is one of the few ubuntu init
scripts lsb compliant so it could be used as lsb resource in a pacemaker
cluster without patching if ubuntu could ship this script with the
suggested check.

Please note that using pacemaker (main repo) in ubuntu is not so easy as
should, I need to path bind9,amavis and apache2 init script to use them
as lsb resource and pure-ftpd RA script (see 1017406). All the issues
are fixable in few minutes maybe these small patches should be shipped
in the default packages,

the bugs reported affect at least oneiric and precise

bye
Nicola

** Affects: apache2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1018171

Title:
  apache2 init script report start success too early

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1018171/+subscriptions



More information about the Ubuntu-server-bugs mailing list