On Sat, 7 Jan 2006, Hammond, Robin-David%KB3IEN wrote:
In order to try to diagnose the nagios problem whereby it enteres the
wait state indefinitely, i added some debugging code to commands.c, and
rebuilt nagios 2.0rc1. I am now getting a very strange error
/Warning: Attempting to execute
On Sat, 7 Jan 2006, Hugo van der Kooij wrote:
And 4400:34 may be valid syntax for a IPv6 address.
Should read 4400::34 and not 4400:34
Hugo.
--
I hate duplicates. Just reply to the relevant mailinglist.
[EMAIL PROTECTED] http://hvdkooij.xs4all.nl/
On Sat, 7 Jan 2006, Hugo van der Kooij wrote:
A manual test here:
./check_ping -H 2001:888:10fa:1 -w 100,20% -c 500,50%
check_ping: Invalid hostname/address - 2001:888:10fa:1
I must have run out of coffee. It works in fact well for IPv6 here:
./check_ping -H 2001:888:10fa::1 -w 100,20% -c
load averages: 1.52, 1.44, 1.33 16:41
60 processes: 1 runnable, 54 sleeping, 4 stopped, 1 on processor
CPUstates: 0.0% user, 96.6% nice, 2.1% system, 1.3% interrupt, 0.0%
idle
Memory: 102M Act, 48M Inact, 888K Wired, 8708K Exec, 132M File, 26M Free
Swap: 129M Total, 129M Free
As for 4400::34 It is not a darpa net IP, but the host ip is valid on this
host. In this case the libexec directory had been deleted, possibly by me,
possibly not. re `make install`ing the plugs seems to have worked.
I too need this caffeine level indicator. I hope it will support HTCPCP.
I
-Original Message-
From: [EMAIL PROTECTED] [mailto:nagios-users-
[EMAIL PROTECTED] On Behalf Of Hammond, Robin-David%KB3IEN
Sent: Friday, January 06, 2006 10:02 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] ping hanging.
In order to try to diagnose the
-Original Message-
From: [EMAIL PROTECTED] [mailto:nagios-users-
[EMAIL PROTECTED] On Behalf Of timeless
Sent: Friday, January 06, 2006 11:51 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Why does Socket Timeout immediately send
notification?
I have Nagios
Marc Powell wrote:
It doesn't. It's treated no differently than any other non-OK plugin
state. Nagios only knows about exit codes and there are only 4
possibilities: OK, WARNING, CRITICAL and UNKNOWN. Nagios performs
retries if the state is anything except OK up to max_check_attempts.
Hello all:
I have a problem where I want a more narrowly defined definition of
flapping. Moving back and forth between ok, critical, warning and
unknown states doesn't quite provide the level of discrimination I
need. Because plugins can fail in multiple modes (e.g. with ping I may
exceed ping
