passive checks AGAIN

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Mariano Cunietti
> Sent: Tuesday, July 05, 2005 10:29 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] passive checks AGAIN
> 
> Hello everybody,
> I'm getting crazy to get passive checks to work on Nagios 1.2.
> I've set up everything so that snmp traps sent from Cisco ATM router
> write correctly to nagios.cmd.
> I've set up a service to handle more Virtual lines, and to declare
which
> VRF virtual line is going up or down, using the text space in the
> nagios.cmd line.
> 
> Here's nagios.cmd:
> 
> [1120576366] PROCESS_SERVICE_CHECK_RESULT;atm1-mi;MPLS-VRF;0;milko
> 
> Yet, I was forced by Nagios to set up also a dummy active check
> (check_dummy), otherwise it would refuse to startup.
> 
> services.cfg
> 
> define service {
>         use                             generic-service
>         name                            passive-service
>         is_volatile                     1
>         passive_checks_enabled          1
>         max_check_attempts              10
>         normal_check_interval           1
>         retry_check_interval            1
>         notification_interval           60     ; 2h
>         active_checks_enabled           0
>         notification_period             24x7
>         notification_options            c,r
>         check_command                   check_dummy!3
>         check_period                    24x7
>         check_freshness                 1
>         register                        0
> }
> 
> define service{
>         use                             passive-service
>         host_name                       atm1-mi
>         service_description             MPLS-VRF
>         contact_groups                  admins-SMS
>         }
> 
> checkcommands.cfg:
> 
> define command{
>         command_name    check_dummy
>         command_line    $USER1$/check_dummy $ARG1$
>         }
> 
> Now, the BIG problem is that Nagios parses nagios.cmd, but the status
> reported is the one set in check_command statement, and not the one
> reported in nagios.cmd. So I always get all lines in UNKNOWN(=exit
> status 3) state.
> 
> Any hint? Please help

Do you have retention enabled? If so, read the Retention Notes at
http://nagios.sourceforge.net/docs/1_0/xodtemplate.html.

Does the Scheduling Queue show a valid Next Check time for this service?
It should show 'N/A'. A valid time would indicate a retention problem.

You also have freshness checking enabled but didn't specify your
freshness_check_interval from nagios.cfg. If your
freshness_check_interval is <= 60 seconds you'd probably see the results
above. I'd try disabling freshness checking on this service to see if
that helps resolve the problem. More information on how freshness
checking works can be found at
http://nagios.sourceforge.net/docs/1_0/freshness.html

--
Marc


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
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