"max_check_attempts" being ignored?

[Jason Byrns]

> We've been using Nagios for awhile, but it seems to ignore our 
> "max_check_attempts" setting.  Why would it send out warnings after 
> every host or service check failure?  Can anyone offer suggestions as to 
> how I'd fix this?

I also notice mention of possibly related items in the Nagios docs.  It 
seems to say any service check failure will cause an immediate host 
check.  And if the host check also fails, the service is put into 
immediate hard error status regardless of the max_check_attempts setting.

This sounds like it would cause an immediate notification every time. 
Almost all of our monitoring is simple ping tests, so having it ping for 
both service and host seems redundant to me.  Perhaps I should disable 
service checks completely for any host I'm just pinging?  And just rely 
on host checks for those?

Thanks again if anyone can offer input!

-- 
Jason Byrns
System Administrator, MicroLnk


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null