[Nagios-devel] Passive checks number of ettempts error

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

[Nagios-devel] Passive checks number of ettempts error

Post by Guest »

--e89a8f2354bd63ce3604bf87bd6c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi everybody,

I use Nagios, release 3.2.3, in a distributed environment, with a central
server and several colector servers.

For a long time I=B4m seeing errors on the passive check mechanism on the
central server, as we can see below.

Sometimes, on the central server, the states and number of attempts don=B4t
follow the correct order, going from SOFT2 to HARD4, for example. However,
on the colector server everything is OK.

Log from Central Server:
Host Up[2012-05-05 01:06:48] HOST ALERT: node;UP;HARD;1;TCP OK - 0.005
second response time on port 135
Host Down[2012-05-05 01:05:40] HOST ALERT: node;DOWN;HARD;4;CRITICAL -
Socket timeout after 10 seconds
Host Down[2012-05-05 01:04:16] HOST ALERT: node;DOWN;SOFT;2;CRITICAL -
Socket timeout after 10 seconds
Host Down[2012-05-05 01:02:55] HOST ALERT: node;DOWN;SOFT;1;CRITICAL -
Socket timeout after 10 seconds

Log from Colector Server:
Host Up[05-05-2012 01:06:31] HOST ALERT: node;UP;SOFT;4;TCP OK - 0.005
second response time on port 135
Host Down[05-05-2012 01:05:21] HOST ALERT: node;DOWN;SOFT;3;CRITICAL -
Socket timeout after 10 seconds
Host Down[05-05-2012 01:04:01] HOST ALERT: node;DOWN;SOFT;2;CRITICAL -
Socket timeout after 10 seconds
Host Down[05-05-2012 01:02:41] HOST ALERT: nodeDOWN;SOFT;1;CRITICAL -
Socket timeout after 10 seconds

Has anybody seen this kind of problem? Can someone help me?

Thanks.

--e89a8f2354bd63ce3604bf87bd6c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi everybody,
=A0
I use Nagios, release 3.2.3, in a distributed environment, with a cent=
ral server and several colector servers.
=A0
For a long time I=B4m seeing errors on the passive check mechanism on =
the central server, as we can see below.
=A0
Sometimes, on the central server, the states=A0and number of attempts=
=A0don=B4t follow the correct order, going from SOFT2 to HARD4, for example=
. However, on the colector server everything is OK.
=A0
Log from Central Server:
Host Up[2012-05-05 01:06:48] HOST ALERT: node;UP;HARD;1;TCP OK - 0.005=
second response time on port 135
Host Down[2012-05-05 01:05:40] HOST ALERT: node;DOWN;HARD;4;CRITICAL -=
Socket timeout after 10 secondsHost Down[2012-05-05 01:04:16] HOST ALE=
RT: node;DOWN;SOFT;2;CRITICAL - Socket timeout after 10 secondsHost Dow=
n[2012-05-05 01:02:55] HOST ALERT: node;DOWN;SOFT;1;CRITICAL - Socket timeo=
ut after 10 seconds

=A0
Log from Colector Server:
Host Up[05-05-2012 01:06:31] HOST ALERT: node;UP;SOFT;4;TCP OK - 0.005=
second response time on port 135Host Down[05-05-2012 01:05:21] HOST AL=
ERT: node;DOWN;SOFT;3;CRITICAL - Socket timeout after 10 secondsHost Do=
wn[05-05-2012 01:04:01] HOST ALERT: node;DOWN;SOFT;2;CRITICAL - Socket time=
out after 10 seconds
Host Down[05-05-2012 01:02:41] HOST ALERT: nodeDOWN;SOFT;1;CRITICAL - Socke=
t timeout after 10 seconds
=A0
Has anybody seen this kind of problem? Can someone help me?
=A0
Thanks.
=A0

--e89a8f2354bd63ce3604bf87bd6c--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked