Passive check strange behaviour

[Jose L. Marcos]

Hi folks,

I've defined a passive check to monitor EMS (HP-UX) Hardware 
notification messages. Basically, I've defined a PERL Handle on each 
HPUX clients that make a send_nsca on a passive check service.

Here is the relevant configuration :

----8<------------
define service{
   name                          generic-service
   active_checks_enabled         1
   passive_checks_enabled        0
   parallelize_check             1
   obsess_over_service           1
   check_freshness               0
   notifications_enabled         1
   event_handler_enabled         1
   flap_detection_enabled        1
   retain_status_information     1
   retain_nonstatus_information  1
   register                      0
}

define service{
   use                           generic-service
   host_name                     s123bdtn
   service_description           PING
   is_volatile                   0
   check_period                  24x7
   max_check_attempts            3
   normal_check_interval         5
   retry_check_interval          1
   contact_groups                admins-sol
   notification_interval         120
   notification_period           24x7
   notification_options          c,r
   check_command                 check_ping!100.0,20%!500.0,60%
}

define service{
   host_name                     hp-host
   service_description           EMS
   is_volatile                   0
   check_period                  24x7
   max_check_attempts            3
   normal_check_interval         60
   retry_check_interval          1
   contact_groups                admins-sol
   notification_interval         240
   notification_period           24x7
   notification_options          c,r
   check_command                 check_ping
   active_checks_enabled         0
   passive_checks_enabled        1
}
---8<--------------

On the service display for hp-host, i get the EMS service line with a 
'P' (meaning passive, I guess ;-) ). The problem I face is this :

Let's suppose I've a condition set for this check (I "send_nsca" a 
warning status). Everything is perfectly traped by Nagios, and my 
service goes "Yellow" (warning).

But : when a PING check (I've also defined a PING service, using 
check_ping command) is issued (at a scheduled time, or forced by me), 
the EMS service is affected : I lose the previous status, the new status 
is the result off the check_ping command.

As far as I understand the service definition for a passive check, I 
must define a check_command for that service to work properly (even if 
the command is never issued by nagios)... But my config must have 
something wrong : nagios should not update output on the passive check 
service !

Any clue ?

-- 
	Jose Luis

----------------------------------------------------------------------------
    Y no llegaste a quererme, y eran mis cinco sentidos
     Y no llegaste a quererme, y que desgraciaito he sido
      Y que ha tenido que aborrecerte tanto como te ha querido (Camaron)
----------------------------------------------------------------------------



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390