Re: [Nagios-devel] nsca-2.9 compatability
Posted: Thu Jan 12, 2012 5:57 am
--_000_4288A518A157EC4C8873FEE74F778BF00E9D40WPSDGQHHOPRSTATEF_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Yeah we went through the same thing and had to bite the bullet and increase=
d the nsca and nrpe buffer sizes all at once across the board. It was pain=
ful, but once done it was done.
Dan
From: Andrew Widdersheim [mailto:[email protected]]
Sent: Wednesday, January 11, 2012 7:33 PM
To: [email protected]; [email protected]
Subject: Re: [Nagios-devel] nsca-2.9 compatability
I haven't looked at NRDP much more than you have but it sounds like it woul=
d be a fix to many of NSCA's short comings. The problem for us is the chore=
of switching everything over in one shot.
We don't do that much passively so the check results queue feature is actua=
lly an extra bonus for us in the upgrade. We are actually more interested i=
n the longer output. If there is an easy way to make this more compatible f=
or with older versions than great. If not we can plan a large upgrade of ev=
erything 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, 11 Jan 2012 15:38:44 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [Nagios-devel] nsca-2.9 compatability
On 1/11/12 11:16 AM, Andrew Widdersheim wrote:
I wanted to use Mike Lindsey's new features in nsca-2.9 but found that clie=
nts on 2.7.2 were not able to communicate after updating the server. I foun=
d this on the Nagios bug tracker:
http://tracker.nagios.org/view.php?id=3D78
From what I'm reading it's not possible to have a client and server compile=
d with different MAX_PLUGINOUTPUT_LENGTH. Has this been fixed at all and I'=
m just not finding it?
As far as I'm aware, there's no easy fix for this. If you cannot upgrade y=
our clients, then you can recompile the nsca binary with MAX_PLUGINOUTPUT_L=
ENGTH set back to 512. That should let you use the checkresult directory f=
eature, without breaking compatibility with older clients.
I'll take another look at the source and see if any options jump out at me,=
but I don't know how much effort I should put into it - I think Andreas is=
actively working on a Better Solution.
--
Mike Lindsey
--_000_4288A518A157EC4C8873FEE74F778BF00E9D40WPSDGQHHOPRSTATEF_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
[email protected]</a
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Yeah we went through the same thing and had to bite the bullet and increase=
d the nsca and nrpe buffer sizes all at once across the board. It was pain=
ful, but once done it was done.
Dan
From: Andrew Widdersheim [mailto:[email protected]]
Sent: Wednesday, January 11, 2012 7:33 PM
To: [email protected]; [email protected]
Subject: Re: [Nagios-devel] nsca-2.9 compatability
I haven't looked at NRDP much more than you have but it sounds like it woul=
d be a fix to many of NSCA's short comings. The problem for us is the chore=
of switching everything over in one shot.
We don't do that much passively so the check results queue feature is actua=
lly an extra bonus for us in the upgrade. We are actually more interested i=
n the longer output. If there is an easy way to make this more compatible f=
or with older versions than great. If not we can plan a large upgrade of ev=
erything 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, 11 Jan 2012 15:38:44 -0800
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [Nagios-devel] nsca-2.9 compatability
On 1/11/12 11:16 AM, Andrew Widdersheim wrote:
I wanted to use Mike Lindsey's new features in nsca-2.9 but found that clie=
nts on 2.7.2 were not able to communicate after updating the server. I foun=
d this on the Nagios bug tracker:
http://tracker.nagios.org/view.php?id=3D78
From what I'm reading it's not possible to have a client and server compile=
d with different MAX_PLUGINOUTPUT_LENGTH. Has this been fixed at all and I'=
m just not finding it?
As far as I'm aware, there's no easy fix for this. If you cannot upgrade y=
our clients, then you can recompile the nsca binary with MAX_PLUGINOUTPUT_L=
ENGTH set back to 512. That should let you use the checkresult directory f=
eature, without breaking compatibility with older clients.
I'll take another look at the source and see if any options jump out at me,=
but I don't know how much effort I should put into it - I think Andreas is=
actively working on a Better Solution.
--
Mike Lindsey
--_000_4288A518A157EC4C8873FEE74F778BF00E9D40WPSDGQHHOPRSTATEF_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
[email protected]</a