Service Alerts and Notifications

[Andy Shellam (Mailing Lists)]

Hmm, that's bad news.
In other time settings within in the config you can set "seconds".

I only did this in my new Nagios server build which I haven't gone live 
with yet - the config checker doesn't throw an error so I'd assumed it 
was valid.

Anyone else know this -
In my case what I'd like to do is check each service every 5 minutes, 
then if it goes down, check 10 seconds later 3 times - so after 30 
seconds if it's still down notify me.
One of my routers can be flaky, and at least once a day it will fail a 
Ping check, but succeed straight away with the next one - therefore I 
don't want to have to wait a minute since it failed to find out that 
it's OK.

I was going to alter the interval units setting in the config, but 
Nagios warns that the consequences are untested - anyone have anything 
further on this?

Andy.


wnorth wrote:
> Andy,
>
> 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?
>
> -Wes
>   


-------------------------------------------------------------------------
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