"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?

We're using Nagios 1.2 on a Fedora Core 1 system.  I have Webmin and 
NagMIN 2.1 to allow web-based administration of Nagios.  I notice that 
the cfg files say Flap Detection is enabled, even though NagMIN is 
supposed to be set to disable this.  Would Flap Detection cause trouble 
with max_check_attempts?  Or what?

Thanks very much for any assitance that can be offered!

Here are the relevant config files...

HostTemplate.cfg
----------------
## NagMIN Configuration File (/usr/local/nagmin/nagios/HostTemplate.cfg) 
for HostTemplate
## Generated Fri Jul  2 10:31:34 2004
define host {
     name    generic-host
     max_check_attempts    8
     notification_interval    0
     notification_options    d,r
     notification_period    24x7
     notifications_enabled    1
     check_command    check-host-alive
     checks_enabled    1
     flap_detection_enabled    1
     process_perf_data    1
     retain_status_information    1
     retain_nonstatus_information    1
     event_handler_enabled    1
     register    0
}


ServiceTemplate.cfg
-------------------
## NagMIN Configuration File 
(/usr/local/nagmin/nagios/ServiceTemplate.cfg) for ServiceTemplate
## Generated Fri Jul  2 10:31:34 2004
define service {
     name    generic-service
     check_command    check-host-alive
     check_period    24x7
     notification_period    24x7
     is_volatile    0
     max_check_attempts    8
     normal_check_interval    2
     retry_check_interval    1
     notification_interval    0
     notification_options    c,r
     active_checks_enabled    1
     passive_checks_enabled    1
     parallelize_check    1
     obsess_over_service    1
     check_freshness    0
     notifications_enabled    1
     event_handler_enabled    1
     flap_detection_enabled    1
     process_perf_data    1
     retain_status_information    1
     retain_nonstatus_information    1
     register    0
}
[SNIP: REMAINDER OF SERVICETEMPLATE.CFG]


Host.cfg
--------
## NagMIN Configuration File (/usr/local/nagmin/nagios/Host.cfg) for Host
## Generated Fri Jul  2 10:31:25 2004
define host {
     use    generic-host
     host_name    NAME-REMOVED
     alias    ALIAS REMOVED
     address    IP ADDRESS REMOVED
     parents    PARENT REMOVED
     check_command    check-host-alive
     max_check_attempts    8
     notification_interval    0
     notification_period    24x7
     notification_options    d,r
#   comment    COMMENT REMOVED
}
[SNIP: REMAINDER OF HOST.CFG]


Service.cfg
-----------
## NagMIN Configuration File (/usr/local/nagmin/nagios/Service.cfg) for 
Service
## Generated Fri Jul  2 10:31:34 2004
[SNIP: DNS SERVICE DEFINITION]
define service {
     use    generic-service
     hostgroup_name 
Customers,Fremont,Lincoln,Mosaic,Omaha,Paypal,Saunders,Tekamah,York
     service_description    PING
     contact_groups    admins
     check_period    24x7
     notification_interval    0
     notification_options    c,r
     notification_period    24x7
     check_command    check-host-alive
     max_check_attempts    8
     normal_check_interval    2
     retry_check_interval    1
}
[SNIP: REMAINDER OF SERVICE.CFG]


-- 
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