AW: Please help -- very confused about freshness checking and threshold

[Verstege, Bernhard]

Hi,

I am also confused aubout freshness checks and freshness_threshold.

I want to use it with a distributed monitor, which sends an OK 
of a service every minute via nsca to the master.

The freshness_threshold at the master is set to 180s.

Three minutes after stopping the distributed monitor I see a
warning in the nagios-log of the master and that an immediate
check of this service is forced. Thats what I expected. 

The check_command at the master is something like the stale_service
example seen in the documentation (Just returning a critical_state an echo some text)
.
The check_interval at the master is set to 180s and the max_check_attemps 
is set to 1.

The problem is, that it takes about 20 minutes until the master sends out
a notification.

So, whats wrong ?


Gruß 
B. Verstege
 
-------------------------------------------------------------------------
Bernhard Verstege
Forschungszentrum Karlsruhe GmbH Abt. HIK
Technik und Umwelt
Hermann-von-Helmholtz-Platz 1         Tel.: 0049 7247-82-5665
D-76344 Eggenstein-Leopoldshafen      Fax.: 0049 7247-82-4972
email:  verstege at hik.fzk.de




>-----Ursprüngliche Nachricht-----
>Von: John Fox [mailto:jjf at mind.net]
>Gesendet: Donnerstag, 10. Oktober 2002 21:48
>An: nagios-users at lists.sourceforge.net
>Betreff: [Nagios-users] Please help -- very confused about freshness
>checking and threshold
>
>
>Hello, All,
>
>It appears to me that I've a massive misunderstanding about freshness
>checks and the freshness threshold.
>
>I have some scripts that I use for making and submitting passive
>checks results to my Nagios server.  I run them every three minutes
>via cron, and I have set the freshness threshold to 3600.  Despite
>the seeming overkill of this threshold, my services often go stale
>within just a few minutes of starting Nagios.  A few minutes pass,
>and they then are updated.  It flaps like this persistently.
>
>It seems quite clear to me at this point that I don't understand
>the freshness-checking mechanism, and I'd really appreciate
>some input from those who know the system better than I.
>
>Here is the template I'm using for these particular services:
>
>----
># Diskcheck service definition template
>define service{
>        name                            disk-template   ; 
>Template 'name' - referenced in other service definitions
>        active_checks_enabled           1       ; Active 
>service checks are disabled
>        passive_checks_enabled          1       ; Passive 
>service checks are enabled
>        parallelize_check               1       ; Active 
>service checks should be parallelized (recommeneded)
>        obsess_over_service             1       ; We should 
>obsess over this service (if necessary)
>        check_freshness                 1       ; Default is 
>to NOT check service 'freshness'
>        freshness_threshold             3600    ; Status 
>should be updated every three minutes - this gives lots of wiggle room
>        notifications_enabled           1       ; Service 
>notifications are enabled
>        event_handler_enabled           0       ; Service 
>event handler is enabled
>        flap_detection_enabled          1       ; Flap 
>detection 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
>        max_check_attempts              3
>        normal_check_interval           3
>        retry_check_interval            3
>        check_period                    24x7
>        notification_interval           3
>        notification_period             24x7
>        notification_options            w,c,r,u
>        contact_groups                  systems
>        register                        0       ; Don't 
>register -- it's a template, dummy!
>}
>---
>
>And here's a service definition that makes use of the template:
>
>---
>define service{
>        use                     disk-template
>        host_name               host.domain.name
>        service_description     disk-/usr/local/etc
>        check_command           stale-service-alert
>        }
>---
>
>This has been driving me nuts for a few days now and I'd 
>appreciate any clues as to
>what I've overlooked.
>
>Thanks in advance,
>
>
>John
>+--------------------------------------------------------------
>-------------+
>| John Fox <jjf at mind.net> | System Administrator | Internet 
>Ventures Oregon |
>+--------------------------------------------------------------
>-------------+
>| "You can't talk about George W. without addressing the 
>strange            |
>| Bilbo-Baginnian language that spurts out from between his 
>lips like       |
>| melted marshmallows coming out of a squirt gun." -- Dennis 
>Miller         |
>+--------------------------------------------------------------
>-------------+
>
>
>-------------------------------------------------------
>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
>


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing 
your web site with SSL, click here to get a FREE TRIAL of a Thawte 
Server Certificate: http://www.gothawte.com/rd524.html