Hi there --
What would the correct syntax be? This would apply to a Nagios 2.6 server.
Thanks.
-Original Message-
From: Andy Shellam (Mailing Lists) [mailto:[EMAIL PROTECTED]
Sent: Fri 1/5/2007 5:27 PM
To: Kaplan, Andrew H.
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-use
Some of the checks the check_http will be fine, since it is hitting a page
that accesses the DB layer, so it's a full check. Once we start talking
synthetic transaction monitoring, (e.g. trying to monitor what an end-user
is seeing in terms of query response times, page latency during a work-flow
p
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 un-tested
consequences etc.
Can you not do your web request with the check_http plugin, or does it
require something a bit more complicated?
And
Thanks Patrick that fixed it.
I had to change the interval_length from 60 to 1 which equates to seconds
now instead of minutes I have to specify all my values in seconds, as
follows:
max_check_attempts 3
retry_check_interval 30s
normal_check_interval 300
This causes it to check every 5 minutes,
On Jan 6, 2007, at 12:31 AM, Hugo van der Kooij wrote:
> On Fri, 5 Jan 2007, Darren Dunham wrote:
>
So how do I determine what the proper setting for my timezone is? I
tried setting TZ="America/Anchorage" but this didn't have any
effect.
>>>
>>> That is NOT a valid TZ variable.
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
> After a service (ping) check failed, host state say that host's still
UP.
> That's not what we want to have as we'd like to make a host check and
to know,
> if the host is UNREACHABLE of DOWN. Please, help.
[snip]
> define host{
> name test
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 the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
can you post your definition to your host check command called
"check-host-test-alive" and "check_ping"?
A few more details were nice too.
Is your "PING" Service the only service on that host?
Do you have host checks enabled on your nagio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Miller schrieb:
> Andy Shellam (Mailing Lists) wrote:
>> If I understand it right, your host checks should not be scheduled -
>> but your service checks are.
>> So, every time a service requires checking and Nagios finds the
>> service is down,
hi there!
I know that my question is dull, but I can't find the answer. So,
please, be mercy...
After a service (ping) check failed, host state say that host's still
UP. That's not what we want to have as we'd like to make a host check
and to know, if the host is UNREACHABLE of DOWN. Please, h
On Fri, 5 Jan 2007, Darren Dunham wrote:
>>> So how do I determine what the proper setting for my timezone is? I
>>> tried setting TZ="America/Anchorage" but this didn't have any effect.
>>
>> That is NOT a valid TZ variable. If you take a minute you can use your
>> favorite search engine and actu
13 matches
Mail list logo
