Re: [Nagios-devel] Making passive checks notify like

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] Making passive checks notify like

Post by Guest »

"Marc Powell" writes:

>> -----Original Message-----
>> From: [email protected] [mailto:nagios-devel-
>> [email protected]] On Behalf Of Mark Plaksin
>> Sent: Thursday, August 31, 2006 10:44 AM
>> To: [email protected]
>> Cc: [email protected]
>> Subject: [Nagios-devel] Making passive checks notify like
> activechecks--
>> race condition?
>>
>> We want our passive checks to notify like active checks. What if we
> make
>> a
>
> What do you mean by this? Notifications work exactly the same for both
> active and passive checks.

For us, passive services only notify once per state change. It's been that
way ever since we started using Nagios 1.x. We're running 2.2 now (soon to
be 2.5).

I'll be happy to be told we're just dumb and our config is wrong :) I have
tried and tried to find a problem in our configuration that causes this.
Several threads on the -user list suggest other people have had the same
problem.

We use a service template (below) for both active checks and passive
checks. The only difference being that for passive checks we set these:
active_checks_enabled 0
passive_checks_enabled 1
max_check_attempts 1

Our service template:
define service{
name generic-service ; The 'name' of this service template
is_volatile 0
check_period 24x7
max_check_attempts 3
normal_check_interval 15
retry_check_interval 1
notification_interval 15
notification_period 24x7
notification_options w,c,u,r
notifications_enabled 1 ; Service notifications are enabled
active_checks_enabled 1 ; Active service checks are enabled
passive_checks_enabled 1 ; Passive service checks are enabled/accepted
parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
obsess_over_service 1 ; We should obsess over this service (if necessary)
check_freshness 0 ; Default is to NOT check service 'freshness'
event_handler_enabled 1 ; Service event handler is enabled
flap_detection_enabled 1 ; Flap detection is enabled
failure_prediction_enabled 1 ; Failure prediction is enabled
process_perf_data 1 ; Process performance data
retain_status_information 1 ; Retain status information across program restarts
retain_nonstatus_information 1 ; Retain non-status information across program restarts
register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
}






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked