urday, January 06, 2007 3:48 PM
To: wnorth
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Service Alerts and Notifications
Thanks for the info Wes,
As it appears to work OK I'll try it out on my new box before it goes
live, I was a bit cautious with all the warnings about
t, very powerful...starting to like it more and more. ;-)
>
> -Wes
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Morris,
> Patrick
> Sent: Saturday, January 06, 2007 10:26 AM
> To: Andy Shellam (Mailing Lists)
> Cc: nagios-us
trick
Sent: Saturday, January 06, 2007 10:26 AM
To: Andy Shellam (Mailing Lists)
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Service Alerts and Notifications
> I tried setting the retry value to 30s, and it interpreted it
> as 30 minutes:
>
> max_check_attem
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
> 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
> minut
h Yost'; nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Service Alerts and Notifications
It does thanks much, it makes perfect sense, I didn't even realize that one
can specify the interval in seconds. I am pretty impressed with nagios as
is, compared to thinks like netcoo
erful.
Thanks again,
-Wes
-Original Message-
From: Andy Shellam (Mailing Lists)
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 4:34 PM
To: wnorth
Cc: 'Josh Yost'; nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Service Alerts and Notifications
Don
gt;
> -Original Message-
> From: Josh Yost [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 05, 2007 3:56 PM
> To: [EMAIL PROTECTED]
> Cc: nagios-users@lists.sourceforge.net
> Subject: Re: [Nagios-users] Service Alerts and Notifications
>
> Hi,
> This is kind of
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of wnorth
Sent: Friday, January 05, 2007 4:19 PM
To: 'Josh Yost'
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Service Alerts and Notifications
That is actually interesting, when the host goes down I see a HARD servic
e only way to solve this is to set it at a 1 minute
interval and just wait.
Sound about right?
-Original Message-
From: Josh Yost [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: [EMAIL PROTECTED]
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Serv
for clarification:
By "is that a valid cmd", I mean is the service_notification_command valid?
- Josh
[EMAIL PROTECTED] wrote:
> Hi,
> This is kind of stupid/obvious, but
>
> a) I don't see a HARD service alert in your log snip for the service.
> Did it actually get to that state? Your
Hi,
This is kind of stupid/obvious, but
a) I don't see a HARD service alert in your log snip for the service.
Did it actually get to that state? Your retry interval is 3 min, so it
would take you 15 min or so to get an alert.
b) If it did get to HARD, what was the cmd it tried to run & i
I have setup a few host and HTTP service checks and alerts. When a host goes
down I recieve an email, but when the check_http service fails (e.g. the TCP
port is shutdown on the web server) I see the service alert in the nagios.log
as follows:
[1168038639] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_
13 matches
Mail list logo
