Thanks for your response Hugo.

In this case I have service checks named:

  SSH   # uses check_ssh plugin
  SNMP  # gets a low-latency MIB to ensure SNMPd is answering
SNMP-- $DAEMON ## where $DAEMON is one of many processes that need to be running on the host (each with its own service definition).

In this case SSH does not have any dependencies, it is to be the 'root' check that all the other services should in the end rely on.

The wildcard matches all the process checks over SNMP, and are (intended) to be dependent on the SNMP daemon running properly. The event handlers for these particular services just SSH to the node and restart the service. However to keep this clean I just wanted to make sure that those aren't occuring _unless_ it was confirmed that SNMP and SSH are already running (otherwise the node could be down hard, or it could be responding to a simple death of one of its dependent processes)...

The root issue was an assumption on my part that the service_dependencies did something they did not (i.e., re-checking master states when a child failed a check).

Now that I realize I need to add a SCHEDULE_FORCED_SVC_CHECK to the first run of the event handlers to force a re-check of the state of its master service, I believe I can pull this off properly.

Cheers,

/eli

Hugo van der Kooij wrote:
On Thu, 8 Dec 2005, Eli Stair wrote:


  SSH -- SNMP --\
                 - Ganglia
                 - NTP


define servicedependency{
        host_name                       HOSTNAME1
        service_description             SSH
        dependent_host_name             HOSTNAME1
        dependent_service_description   SNMP
        execution_failure_criteria      w,p,u,c
        notification_failure_criteria   w,p,u,c
        inherits_parent                 1
}


Here you asume that if SSH fails because it depends on another service it
will also fail SNMP

I have not seen SSH being dependent on anything however in your
description. How a non exsiting parent will impact services is unknown to
me.


define servicedependency{
        host_name                       HOSTNAME1
        service_description             SNMP
        dependent_host_name             HOSTNAME1
        dependent_service_description   SNMP--*
        execution_failure_criteria      w,p,u,c
        notification_failure_criteria   w,p,u,c
        inherits_parent                 1
}


Is this a real wildcard? Are they supported?

I would expect:

define servicedependency{
          host_name                       HOSTNAME1
          service_description             SNMP
          dependent_host_name             HOSTNAME1
          dependent_service_description   NTP
          execution_failure_criteria      w,p,u,c
          notification_failure_criteria   w,p,u,c
          inherits_parent                 1
}

define servicedependency{
          host_name                       HOSTNAME1
          service_description             SNMP
          dependent_host_name             HOSTNAME1
          dependent_service_description   Ganglia
          execution_failure_criteria      w,p,u,c
          notification_failure_criteria   w,p,u,c
          inherits_parent                 1
}


Hugo.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to