--_1e26b84b-061f-4267-bb21-7042e5ad6432_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I haven't looked at NRDP much more than you have but it sounds like it=20
would be a fix to many of NSCA's short comings. The problem for us is=20
the chore of switching everything over in one shot.=20
We don't do=20
that much passively so the check results queue feature is actually an=20
extra bonus for us in the upgrade. We are actually more interested in=20
the longer output. If there is an easy way to make this more compatible=20
for with older versions than great. If not we can plan a large upgrade=20
of everything or a cut over to NRDP. We just have a problem now and were
looking for a quick solution without breaking already existing stuff.=20
-Andrew W.=20
Date: Wed=2C 11 Jan 2012 15:38:44 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [Nagios-devel] nsca-2.9 compatability
=20
=20
=20
=20
On 1/11/12 11:16 AM=2C Andrew Widdersheim wrote:
=20
=20
=20
I wanted to use Mike Lindsey's new features in nsca-2.9 but
found that clients on 2.7.2 were not able to communicate after
updating the server. I found this on the Nagios bug tracker:
=20
http://tracker.nagios.org/view.php?id=3D78
=20
From what I'm reading it's not possible to have a client and
server compiled with different MAX_PLUGINOUTPUT_LENGTH. Has this
been fixed at all and I'm just not finding it? =20
=20
=20
As far as I'm aware=2C there's no easy fix for this. If you cannot
upgrade your clients=2C then you can recompile the nsca binary with
MAX_PLUGINOUTPUT_LENGTH set back to 512. That should let you use
the checkresult directory feature=2C without breaking compatibility
with older clients.
=20
I'll take another look at the source and see if any options jump out
at me=2C but I don't know how much effort I should put into it - I
think Andreas is actively working on a Better Solution.
--=20
Mike Lindsey =
--_1e26b84b-061f-4267-bb21-7042e5ad6432_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I haven't looked at NRDP much more than you have but it sounds like it=20
would be a fix to many of NSCA's short comings. The problem for us is=20
the chore of switching everything over in one shot. We don't do=20
that much passively so the check results queue feature is actually an=20
extra bonus for us in the upgrade. We are actually more interested in=20
the longer output. If there is an easy way to make this more compatible=20
for with older versions than great. If not we can plan a large upgrade=20
of everything or a cut over to NRDP. We just have a problem now and were
looking for a quick solution without breaking already existing stuff. =
-Andrew W. Date: Wed=2C 11 Jan 2012 15:38:44 -0800From: mike-nagios=
@5dninja.netTo: [email protected]: awiddersheim@=
hotmail.comSubject: Re: [Nagios-devel] nsca-2.9 compatability
=20
=20
=20
=20
On 1/11/12 11:16 AM=2C Andrew Widdersheim wrote:
.ExternalClass .ecxhmmessage P
{padding:0px=3B}
.ExternalClass body.ecxhmmessage
{font-size:10pt=3Bfont-family:Tahoma=3B}
I wanted to use Mike Lindsey's new features in nsca-2.9 but
found that clients on 2.7.2 were not able to communicate after
updating the server. I found this on the Nagios bug tracker:
http://tracker.nagios.org/view.php=
?id=3D78<
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]