Freshness Threshold PERIOD FUNCTION

[Stephan Janosch]

Horvath Tamas wrote:
> Hi Stephan!
> 
> As I know in Nagios 1.2 there is no check_period directive for hosts,
> because: "Unlike service checks, host checks are not scheduled on a regular
> basis. Instead they are run on demand, as Nagios sees a need."
> 
>  
> However I configued 'none' timeperiod for the check_ping service associated
> to this host, because I would like, that nobody can start an active check
> from the web interface.
> 
> Accoring to Nagios 1.2's Service Result Freshness Checks document
> (http://nagios.sourceforge.net/docs/1_0/freshness.html): "It is important to
> note that an active service check which is being forced because the service
> was detected as being "stale" gets executed even if active service checks
> are disabled on a program-wide or service-specific basis."
> 
> So, what I wrote is a normal Nagios behavior and I need the check_ping
> command and Service Result Freshness option! When Nagios says: VPNC DOWN, is
> true!!! However it would be better, if Nagios will live the last non-stale
> state and doing Service Result Freshness checking only when I need it.
> 
> But I will try another time period instead of none, maybe it helps. We never
> know:)
> 
> Is there any nother suggestion???
> 
> 
> Thanks, Tamas
> 
> 
> -----Original Message-----
> From: Stephan Janosch [mailto:stephan.janosch at interface-business.de] 
> Sent: Friday, January 28, 2005 3:25 PM
> To: Horvath Tamas
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Freshness Threshold Period
> 
> Horvath Tamas wrote:
> 
>>Hi List members!
>>
>>I use Nagios 1.2, plugins 1.4beta1, Debian 3.1.
>>
>>I connect to the monitored network via VPN. I have to monitor this network
>>from 15.20 to next day 8.00.
>>
>>I use a passive check to check the VPN connection status.
>>
>>My check command is check_ping, check_period is none and
> 
> notification_period
> 
>>is 15.20-8.00, Freshness Threshold is 900 s. Nagios is not running from
>>10.00 to 11.50 every weekday.
>>
>>My problem: After 8.00 the VPN connection is teared down nomally. The
>>Freshness Threshold is elapsed and Nagios runs the check_ping command, and
>>eventually Nagios marks the VPN Concentrator host as Down.
>>
>>It is ok, but annoying. I think I need a " Freshness Threshold period"
>>feature which says, that Nagios has not to run active checks beyond these
>>periods. This is however not implemented and I'm not a programmer.
>>
>>How can I solve this annoying problem easier?
>>
>>Thanks in advance!
>>
>>Tamas.
>>
Hi Tamas!

i have an idea here, but no clue whether it will work.

Perhaps you can make a check_period, which allows active checks between 
15.20 and 8.00. To prevent somebody to switch on active checks, you 
probably modify your nagios authorisations.

Your setup is quiet tricky. *g*

Stephan



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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