Host Status: UP
(for 0d 19h 19m 15s) Status Information: FPING OK - 65.106.232.209
(loss=0%, rta=41.000000 ms) Performance Data: loss=0%;80;100;0;100
rta=0.041000s;2.000000;5.000000;0.000000 Current Attempt: 1/3 (HARD
state) Last
Check Time: 06-19-2009 10:13:39 Check Type: ACTIVE Check Latency /
Duration: 56.436 / 2.537
seconds Next Scheduled Active Check: 06-19-2009 10:14:47 Last State
Change: 06-18-2009 14:58:37 Last Notification: N/A (notification 0) Is This
Host Flapping? N/A In Scheduled Downtime? NO
Last Update: 06-19-2009 10:17:38 ( 0d 0h 0m 14s ago)
As per above the host is scheduled to check every 1 min. The parameter in
use is "check_interval =1 " also "retry_interval=1"
Then when the host went down the " View alert history for this host" at the
left corner says :
[image: Host Down][06-18-2009 14:38:40] HOST ALERT:
benroutermr;DOWN;HARD;3;FPING CRITICAL - 65.106.232.209 (loss=100% )
[image: Host Down][06-18-2009 14:32:56] HOST ALERT:
benroutermr;DOWN;SOFT;2;FPING CRITICAL - 65.106.232.209 (loss=100% )
[image: Host Down][06-18-2009 14:32:40] HOST ALERT:
benroutermr;DOWN;SOFT;1;FPING CRITICAL - 65.106.232.209 (loss=100% )
Why is it not checking every minutes when "retry_interval=1" ? ?
Because of this notification is getting delayed , i want the notification to
be sent 3 min after the host is down.
--
Best Regards
Param S
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Nagios-users mailing list
Nagios-users@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
