Passive checks and retry_check_interval

[Douglas E. Warner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a question about how retry_check_interval is used when active and 
passive checks are being used for a service.
When a passive check is submitted in a Critical state, is the next scheduled 
active check the normal check, or the retry check?

I think I have a unique setup; I have a ton of interfaces I check on my 
network and generally use traps to trip when they go up or down (Passive 
check).  I wanted to decrease the noise this caused and do active checks 
periodically as well to make sure things are okay, and to recheck the passive 
result to make sure it lasted, so I have active checks set to run every 60 
minutes, and rechecks at 3 minutes.
The problem I'm seeing is that an interface that was marked critical by a 
passive check was not scheduled to be checked for another 43 minutes; where I 
thought it should be 3 min or less.  My execution latency is reported as 5 
sec, and check latency as 9 seconds, so I don't think that my server is 
overloaded.

If I need to setup an event handler to reschedule the check to happen now (or 
3 minutes from now), I can do that, but I just need to know if this is 
intended or expected behavior.

- -Doug

- -- 
Douglas E. Warner    <dwarner at ctinetworks.com>     Network Engineer
CTI/PAdotNET         http://ctinetworks.com        +1 717 975 9000
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/ecz9JV36su0A0xIRAqSFAKD35ibJCgT2LW3hzdvMZ96EZQG7wwCgqO85
WUTlRub8Uwa+A+klYe71jlU=
=sb8R
-----END PGP SIGNATURE-----



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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