Service Alerts and Notifications

Morris, Patrick patrick.morris at hp.com
Sat Jan 6 19:25:34 CET 2007


> I tried setting the retry value to 30s, and it interpreted it 
> as 30 minutes:
> 
> max_check_attempts 3
> retry_check_interval 30s
> normal_check_interval 5
> 
> I would have thought the above would set a HARD alert after 
> 1.5 minutes, but it checked, then scheduled the next check 30 
> minutes later. Is there a global setting somewhere that I 
> missed that needs to be changed from minutes to seconds?

Check your interval_length in nagios.cfg.  That determines how long a
single unit it.

If "30" gives you 30 minutes, then it's probably set to 60 (60 seconds/1
minute).  Sticking an "s" on your retry interval isn't going to change
anything; it'll just be ignored.

You'll need to adjust your interval if you want things to happen in
under 1 time unit (in the default case, 60 seconds).

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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