On Wed, Apr 04, 2012 at 11:21:15AM -0500, Dimitri Maziuk wrote: > On 04/04/2012 10:59 AM, Dejan Muhamedagic wrote: > > Hi, > ... httpd monitor ... > > It may be wrong or not, that depends on what you need. > > (Another questionable choice as I recall was to consider 4xx an error. > Dep. on what you need, you may want to treat only some 5xx codes as > errors b/c the others mean apache is up and answering properly.)
Isn't the status page always supposed to return, well, the status? For the depth 10 test, we may change the test (btw, it seems like not many people are using that). Patches welcome :) > > 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. > > Which is precisely what I do: I monitor on the host with (more or less) > "lsof -i | grep httpd.+\*:http" How is that better than fetching the status page? > and I've nagios in another subnet > checking the actual webpages. (Obviously, there's then gateways and > switches and all that...) Good! Cheers, Dejan > -- > Dimitri Maziuk > Programmer/sysadmin > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
