<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59"> <TITLE>RE: [Nagios-users] alerting flakey</TITLE> </HEAD> <BODY>  OK. It's definatly none of those. take a look. define service{ use local-service hostgroup_name cisco_routers service_description Cisco_load check_command check_snmp_load_cisco!cisco!90,80,60!100,100,100 } ############## define service{ name local-service ; The name of this service template use generic-service ; Inherit default values from the generic-service definition check_period 24x7 ; The service can be checked at any time of the day max_check_attempts 4 ; Re-check the service up to 4 times in order to determine its final (hard) state normal_check_interval 5 ; Check the service every 5 minutes under normal conditions retry_check_interval 1 ; Re-check the service every minute until a hard state can be determined contact_groups admins ; Notifications get sent out to everyone in the 'admins' group notification_options w,u,c,r ; Send notifications about warning, unknown, critical, and recovery events notification_interval 60 ; Re-notify about service problems every hour notification_period 24x7 ; Notifications can be sent out at any time register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! } ############## Whether a critical alert gets generated or not can depend on the notification_options in the service definition, the host definition and/or the contact definition. Whether notifications are generated at all can depend on notification_enabled in the host or service definition, on the timeperiod in the contact definition, globally in the nagios configuration and it can be dynamically enabled/disabled for hosts, services and for nagios as a whole. My guess is that it might be something quite simple in the notification_options somewhere. See <A HREF="http://nagios.sourceforge.net/docs/2_0/notifications.html">http://nagios.sourceforge.net/docs/2_0/notifications.html</A> Another option worth trying is check_for_orphaned_services in your main nagios.cfg file. See: <A HREF="http://nagios.sourceforge.net/docs/2_0/configmain.html#check_for_orphaned_services">http://nagios.sourceforge.net/docs/2_0/configmain.html#check_for_orphaned_services</A> Cheers, Jim ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash <A HREF="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </BODY> </HTML>