On May 20, 2009, at 8:22 AM, Anirudh Srinivasan wrote:
> This is how i wanted to make it look like :
>
> [05-19-2009 13:34:00] HOST ALERT: app-engbw5;DOWN;HARD;3;FPING
> CRITICAL - (loss=100% )
> [05-19-2009 13:33:00] HOST ALERT: app-engbw5;DOWN;SOFT;2;FPING
> CRITICAL - (loss=100% )
>
> [05-
This is how i wanted to make it look like :
[05-19-2009 13:34:00] HOST ALERT: app-engbw5;DOWN;HARD;3;FPING CRITICAL -
(loss=100% )
[05-19-2009 13:33:00] HOST ALERT: app-engbw5;DOWN;SOFT;2;FPING CRITICAL -
(loss=100% )
[05-19-2009 13:32:00] HOST ALERT: app-engbw5;DOWN;SOFT;1;FPING CRITICAL -
(los
No, please check your "Scheduling Queue", view "Last Check" and "Next Check".
Please distinguish "check history" and "alert history".
Are you sure you want check max 4 times, and alter every 1 minuties ?
The your "check_interval" should be 12s, it's too short!
In 'nagios.cfg', set 'interval_leng
Hi Dongsheng
I tried as you suggested by putting
Check_interval 1
retry_interval 1
max_check_attempts 3
But this is what i see on the alert history :
[05-19-2009 13:42:35] HOST ALERT: app-engbw5;DOWN;HARD;3;FPING CRITICAL -
(loss=100% )
[05-19-2009 13:37:38] HOST ALERT: ap
On May 18, 2009, at 10:19 PM, Anirudh Srinivasan wrote:
> Also one more question :
>
> How was nagios managing that retry_interval earlier when this
> parameter was not even set ??
Are you certain that it's not? It's a required parameter under 2.x and
while I can't test it, I have no reason
On May 18, 2009, at 10:07 PM, Anirudh Srinivasan wrote:
> Hi
>
> Thanks for the reply , will try this out. But is there some
> centralized Parameter in nagios.cfg that could solve this issue.
No, it's defined per host and service. You could use templates though
to 'centralize' it (or assign
Also one more question :
How was nagios managing that retry_interval earlier when this parameter was
not even set ??
Is it because of SMART calculation thats set in nagios.cfg ??? If not please
can i know how that worked ???
2009/5/18 Anirudh Srinivasan
> Hi
>
> Thanks for the reply , will try
Hi
Thanks for the reply , will try this out. But is there some centralized
Parameter in nagios.cfg that could solve this issue.
Thanks in Adv
On Mon, May 18, 2009 at 11:01 PM, Dongsheng Song
wrote:
> In service definition, set:
>
>check_interval 1
>retry_interva
Hi,
Anirudh Srinivasan wrote:
>
> Below is the Alert history for the the host , and the max_check_attemps
> is = 5
>
> If you could notice the check frequency is approx= 3 min .
>
> Is it possible to reduce this parameter, if yes then what is the
> parameter that i have to look for.
> I do
In service definition, set:
check_interval 1
retry_interval 1
max_check_attempts 5
In host definition, set:
check_interval 1
retry_interval 1
max_check_attempts
Hi Nagios experts:
Below is the Alert history for the the host , and the max_check_attemps is =
5
[05-11-2009 16:46:57] HOST ALERT: benfwca;DOWN;HARD;5;FPING CRITICAL
- (loss=100% )
[05-11-2009 16:43:36] HOST ALERT: benfwca;DOWN;SOFT;4;FPING CRITICAL
- (loss=100% )
[05-11-2009 16:40:30] HOST AL
11 matches
Mail list logo
