They are using nrpe_nt. We never had a problem with the 1.2 machine.
It is only the 2.5 machine and they are configured the same as far as
check intervals are concerned.
On 9/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote on 14/09/2006 19:30:29:
>
> > The device th
[EMAIL PROTECTED] wrote on 14/09/2006 19:30:29:
> The device that is detecting the "attack" is a content switch, which
> sits in front of all the hosts. There isn't a particular command that
> is triggering the alert.
>
> Here are two that I have seen for sure:
>
> define service {
> name
The device that is detecting the "attack" is a content switch, which
sits in front of all the hosts. There isn't a particular command that
is triggering the alert.
Here are two that I have seen for sure:
define service {
name check_nt_cpu
check_command check_nt_cpu!!foo!10,90
Did the 'ping' command check itself change from the 2 different
versions ? Check in checkcommands.cfg, see if the command definition is
the same between the two.
-DL
On Thu, 2006-09-14 at 17:07 +0100, [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote on 14/09/2006 17:00:29:
>
> > Good morning,
[EMAIL PROTECTED] wrote on 14/09/2006 17:00:29:
> Good morning,
>
> I have 2 nagios servers. One is running 1.2 and the other is running
> 2.5. Both are running in parallel while I migrate to the 2.5 machine.
> Our content switch is detecting that the 2.5 machine is SYN attacking
> hosts. Bot
Good morning,
I have 2 nagios servers. One is running 1.2 and the other is running
2.5. Both are running in parallel while I migrate to the 2.5 machine.
Our content switch is detecting that the 2.5 machine is SYN attacking
hosts. Both servers have very similar monitoring sets and similar
confi
