On 10/24/2012 02:20 PM, Lars Marowsky-Bree wrote: > On 2012-10-24T13:17:57, Dimitri Maziuk <[email protected]> wrote: > >> I have e.g. mon script that greps 'lsof -i' to see if httpd is listening >> on * or cluster ip. Which IMO is a way saner check than wget'ting >> http://localhost/server-status -- and treating a [34]04 as a fail. Hence >> the "plus" quip. ;) > > That the process is there and listening does not at all equal that it is > responding.
No it isn't. However, *apache* listening and not answering is something I've never seen ever. One scenario where I can see that happening is kernel completely stuck in something like sata driver retry loop, in which case the monitoring task is stuck as well. That's the sort of thing you run nagios elsewhere for. But that's not the only problem between the author's chair and keyboard there: how about responding with a 404 = fail. Or using the uri that has no business being enabled on a production server. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
