Hi, On Tue, Apr 03, 2012 at 01:18:39PM -0500, Dimitri Maziuk wrote: > On 04/03/2012 06:53 AM, David Gubler wrote: > > Hi list, > > > > I've been experimenting with Heartbeat/Pacemaker on Ubuntu 11.10 > > (Pacemaker 1.1.5 and Heartbeat 3.0.5) and I have hit a very nasty issue > > with the apache resource agent. > ... > > Thus, the monitor operation did time out instead of wget (thus, > > pacemaker thinks that the monitor itself has failed instead of the > > service it is monitoring, which is semantically just plain wrong, IMHO). > > If it's the same resource agent I saw back when: the one that fetches > /server-status, s/semantically// -- it's just plain wrong.
It may be wrong or not, that depends on what you need. If you need deeper testing, use depth 10 and testurl or testconffile. > Basically, if it's running on the same node as apache, the kernel should > be smart enough to route it via lo even if you explicitly ask wget to > hit the cluster ip. So it's not checking if httpd is answering where you > actually care. At any rate, tests are always running from the same host where the server is running. If you want to test "where you actually care", then you'd need to be a bit closer to your clients and use other kind of monitoring. Thanks, Dejan > FWIW > -- > Dimitri Maziuk > Programmer/sysadmin > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
