[Linux-cluster] application monitoring - apache crash doesn't invoke failover

[Eric Kerin]

See this bugzilla entry:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151104 especially
the attached patch.

Basically RHEL4 (and RHEL3) don't (and at this point, can't) follow the
LSB's standard return value for successful stop operations, which is
that a stop operation of a service that isn't running should return 0 as
it's errorlevel.

Thanks,
Eric Kerin
eric at bootseg.com



On Wed, 2005-10-19 at 12:27 -0700, Alexander Rau wrote:
> We are trying to test the failover in a 2 cluster
> environment by killing apache.
> 
> The service fails according to clustat, however the
> cluster mananger does not move the service from the
> failed node to the fail over node....
> 
> /var/log/messages shows the following output (on the
> node with the forced failure):
> 
> Oct 19 16:34:59 armstrong clurgmgrd[4269]: <notice>
> status on script "httpd" returned 1 (generic error)
> Oct 19 16:34:59 armstrong clurgmgrd[4269]: <notice>
> Stopping service http
> Oct 19 16:34:59 armstrong httpd: httpd shutdown failed
> Oct 19 16:34:59 armstrong clurgmgrd[4269]: <notice>
> stop on script "httpd" returned 1 (generic error)
> Oct 19 16:34:59 armstrong clurgmgrd[4269]: <crit> #12:
> RG http failed to stop; intervention required
> Oct 19 16:34:59 armstrong clurgmgrd[4269]: <notice>
> Service http is failed
> 
> Anybody any ideas?
> 
> Thanks
> 
> AR
> 
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster