<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>I had a similar problem with passive checks and freshness
checking when I upgraded to 2.0. I am guessing (though no one ever responded
when I asked the list before) That they changed the logic. Before a stale check
would trigger an active check in all cases regardless of the check period. Now
it appears that check_period overrides that.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>ie. Whereas </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>check_period = none</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>active_check_enabled = 1</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>used to work, now you have to use</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>check_period = 24x7</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>active_checks_enabled = 0</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>Which is a little annoying, in that the gui now puts the
"pasv" icon next to all your passive checks, and the tac cgi wont consider a
passive failed check to be an unhandled problem by default. This is a bug in my
opinion, though no one seems to agree with me. (assuming silence indicates
disagreement.)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>Anyway. below is the config i use..</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>define
service{<BR>
name
audit-service-tmpl ; template for Passive commands (like Replication Check
Services<BR>)<BR>
is_volatile
1
; notify with every failure (with freshness checks)
<BR>
check_period
24x7
<BR>
max_check_attempts
1<BR>
normal_check_interval
1<BR>
retry_check_interval
1<BR>
retain_status_information
1<BR>
retain_nonstatus_information
1
; <BR>
passive_checks_enabled
1
; these are all passive
checks<BR>
active_checks_enabled
0
; these are all passive
checks<BR>
flap_detection_enabled
0
; don't want flaps detected in these
cases.<BR>
notification_interval
31536000<BR>
notification_period
24x7<BR>
notification_options
w,u,c,r<BR>
check_freshness
1<BR>
register
0<BR>}<BR></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925294713-04012006><FONT face=Arial
color=#0000ff size=2>define
service{<BR>
service_description
rhost_check<BR>
host_name
audit<BR>
contact_groups
unix-admins<BR>
check_command
check-freshness-stale!"rhost audit did not report on
time" ; dont forget to give script
details<BR>
freshness_threshold
90000 ; 25 hours (seconds) make this number be a
couple of hours after next job should
complete<BR>
use
audit-service-tmpl<BR>}<BR></DIV></FONT></SPAN><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Cott Lang
[mailto:cott@internetstaff.com] <BR><B>Sent:</B> Tuesday, January 03, 2006
10:30 PM<BR><B>To:</B> nagios-users@lists.sourceforge.net<BR><B>Subject:</B>
[Nagios-users] 2.0 upgrade, passive checks problem<BR></FONT><BR></DIV>
<DIV></DIV>I've had passive checks working for several years in 1.x, with
never a hitch.<BR><BR>Unfortunately, that all changed when I upgraded to
2.0. Suddenly, freshness checks never occurred. Ever.<BR><BR>I've
re-read the docs several times, my config seems okay. My first problem seems
to be that my "check_period" under 1.x was always "none", which worked
fine.<BR><BR>If I change it to "24x7", I start getting freshness checks.
However, they seem to totally ignore freshness_threshold and use the
normal_check_interval. If I comment out freshness_threshold and define
normal_check_interval to what I want, I seem to get random
values.<BR><BR>i.e., a service set to 10 minutes tells me
this:<BR><BR>[1136344804] Warning: The results of service 'x' on host y are
stale by 12 seconds (threshold=821 seconds). I'm forcing an immediate
check of the service.<BR><BR>Where'd 821 seconds come from?<BR><BR>Worse, I
have other services with nearly identical definitions that don't indicate they
are stale or that a freshness check is being scheduled, but suddenly go
critical:<BR><BR>[1136344634] SERVICE ALERT:
host;service;CRITICAL;HARD;1;CRITICAL: service success not reported<BR><BR>The
normal_check_interval is set to 2 hours, but it seems to go critical every
~10-15 minutes. <BR><BR>I'm at a loss at this point, I can only "kinda" get
passive checks working. It seems like I must be missing something obvious here
in the 2.0 upgrade, but I'm befuddled. I've been using a template for
all my passive services like this:<BR><BR><BR>define service {<BR>
name
passive-service<BR>
active_checks_enabled
0 ; Active service checks are
enabled<BR>
passive_checks_enabled
1 ; Passive service checks are
enabled/accepted<BR>
parallelize_check
1 ; Active service checks should be
parallelized<BR>
obsess_over_service
1 ; We should obsess over this service (if
necessary)<BR>
check_freshness
1 ; Default is to NOT check service
'freshness'<BR>
notifications_enabled
1 ; Service notifications are
enabled<BR>
event_handler_enabled
1 ; Service event handler is
enabled<BR>
flap_detection_enabled
1 ; Flap detection is enabled<BR>
process_perf_data
1 ; Process performance data<BR>
retain_status_information
1 ; Retain status information across
program restarts<BR> retain_nonstatus_information
1 ; Retain non-status information across
program restarts<BR>
max_check_attempts
1<BR>
normal_check_interval
1560 ; 26 hours<BR>
retry_check_interval
1<BR>
is_volatile
0<BR>
check_period
24x7<BR>
notification_interval
15<BR>
notification_period
24x7<BR>
notification_options
w,c,r<BR> ;
freshness_threshold
93600 ; 26 hours appears useless!<BR>
register
0<BR>}<BR><BR>Any help would be
appreciated!<BR><BR>thanks!<BR><BR><BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>