Service Dependencies "wildcarding" error ?

[Paulo Pinto]

Ok, my mistake.

I've just upgraded from 1.0b5 to 1.0b6 and the wildcards on service dependencies work as expected.

To Jim Carroll:

If you want to be ... hmm .. a bit paranoid about the tests, I'd suggest you to run something like NSClient (windows) or netsaint_statd (*nix) on the client machines and then check for the availability of your NRPE daemon (using check_named_proc or similar).

On the other hand, to make things a *LOT* easier, just choose one of your NRPE checked services, nominate it as your 'master' service and make all the other NRPE checked services dependent of it. At least, if the daemon fails, you'll get only one notification.

I wouldn't go for check_tcp ... I personally don't like the idea :) (sometimes, a returned banner isn't a proof that the service is healthy ... )

Hugz all.
  ----- Original Message ----- 
  From: Carroll, Jim P [Contractor] 
  To: 'Paulo Pinto' ; Scott ; nagios-users at lists.sourceforge.net 
  Sent: Wednesday, October 16, 2002 4:26 PM
  Subject: RE: [Nagios-users] Service Dependencies "wildcarding" error ?


  Paulo, that looks like an excellent scenario to streamline!

  At some point I'll be trying my hand at service dependencies.  Here's the scenario I hope to streamline:

  - host1 is running NRPE
       - nrpe.cfg has several tests configured
  - most other hosts will be similarly configured with NRPE
  - some hosts will be running a superset of the NRPE definitions

  Risk in this scenario:  if the NRPE daemon is down and Nagios starts checking those services, naturally it will fail for each and every NRPE service test defined.

  Goal:  If NRPE is down, be notified that NRPE is down.  Silence on all the NRPE tests.

  Actually, I wouldn't mind some input on one aspect of setting this up.  I'm torn between making one of the NRPE tests the service depended on by the other NRPE tests (for a given host), versus just using check_tcp to verify that the NRPE daemon is up and listening.  Thoughts anyone?

  jc
    -----Original Message-----
    From: Paulo Pinto [mailto:japh at ip.pt]
    Sent: Wednesday, October 16, 2002 7:07 AM
    To: Scott; nagios-users at lists.sourceforge.net
    Subject: Re: [Nagios-users] Service Dependencies "wildcarding" error ?


    Hi.

    Imagine the following scenario:

    - 2 web servers, with 50 Vhosts each.
    - 1 Alteon webswitch, virtualizing the 50 Vhosts
    - Nagios is monitoring the 150 webservices. A failed service gets notified by SMS. 

    Now, without service dependencies, if a webserver goes down, you get 50 SMS. If BOTH webservers go down, you get 150SMS. 

    WITH service dependencies, you can make your webtests depend on the RealServers status on the Alteon... if 1 webserver goes down, you get 1 SMS, if both go down you got 2 sms.
    That's why :-)

    Anyway, I've already seen in the changelog that wildcarding was addedd on 1.0b6 (I'm running beta5) ... I'll upgrade it and see if it works :-)

    Hugz all.

      ----- Original Message ----- 
      From: Scott 
      To: Paulo Pinto ; nagios-users at lists.sourceforge.net 
      Sent: Wednesday, October 16, 2002 11:32 AM
      Subject: Re: [Nagios-users] Service Dependencies "wildcarding" error ?


      how canb a service be dependant on all services like this? wouldnt you just have a host dependancy and be done with it?
        ----- Original Message ----- 
        From: Paulo Pinto 
        To: nagios-users at lists.sourceforge.net 
        Sent: Tuesday, October 15, 2002 11:00 AM
        Subject: [Nagios-users] Service Dependencies "wildcarding" error ?


        Hi all.

        I'm trying to setup service dependencies.

        In my case, I want ALL services in host A to be dependent of service SERVICE on host B.

        So, I've configured dependencies.cfg like this:

        define servicedependency{
                host_name                       HOST-B
                service_description             SERVICE
                dependent_host_name             HOST-A
                dependent_service_description   *
                execution_failure_criteria      n
                notification_failure_criteria   u,c
                }


        Guess what:

        $ /path/to/nagios/bin/nagios -v /path/to/nagios/etc/nagios.cfg

        (...)
        Error: Dependent service specified in service dependency for service '*' on host 'HOST-A' is not defined anywhere!
        Error: Dependent service specified in service dependency for service '*' on host 'HOST-A' is not defined anywhere!
        (...)

        I'm using Nagios 1.0b5, btw

        Any hints ?

        Hugz,

        Japh




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20021016/e4322caf/attachment.html>