Check_freshness does not obey Freshness_threshold

Andre Bergei andre.bergei at ementor.no
Fri Nov 28 17:03:58 CET 2003


Hi group.

 I have a distributed enviroment with check_freshness defined on my
central, but services are marked stale before
Mye threshold setting has expired.

As you see from my nagios.log under, my threshold is 600 seconds, but my
central does the check even if the service is stale by just 1 second.

	Log example
"
[1070033901] Warning: The results of service 'sysuptime' on host
'hostnamehere' are stale by 70 seconds (threshold=600 seconds).  I'm
forcing an immediate check of the service.
"
 thus the central does an active check of the service before the
threshold setting says it's okay to do so.
 Anyone seen this problem before?  


	Nagios compile switches;
./configure  --prefix=/opt/nagios --datadir=/var/data/nagios/share
--with-nagios-user=nagios --with-nagios-grp=nagios --with-mysql-status
--with-nagios-grp=nagios --with-mysql-status --with-mysql-lib=/usr/lib
* note Mysql status support compiled in only for status data.

	My services template on the central
define service{
        ; The 'name' of this service template, referenced in other
service definitions
        name                            root_template_100nooslnam100
        active_checks_enabled           0       
        passive_checks_enabled          1       
        parallelize_check               1       
        obsess_over_service             0      
        check_freshness                 1       
        freshness_threshold             600     
        notifications_enabled           1       
        event_handler_enabled           1       
        flap_detection_enabled          1       
        process_perf_data               1       
        retain_status_information       0       
        retain_nonstatus_information    0       
        notification_options            w,u,c,r
        name                            generic-bmk
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           5
        retry_check_interval            1
        contact_groups                  router-admins
        notification_interval           240
        notification_period             24x7
        register                        0
        }


	the nagios.cfg got these values defined for freshness
# check the "freshness" of service results.  Enabling this option
# Values: 1 = enabled freshness checking, 0 = disable freshness checking
check_service_freshness=1
# check the "freshness" of service check results.  If you have
# disabled service freshness checking, this option has no effect.
freshness_check_interval=300
	


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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





More information about the Users mailing list