<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Mangal;
panose-1:0 0 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Mangal;
panose-1:0 0 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yeah we went through the same thing and had to bite the bullet and increased the nsca and nrpe buffer sizes all at once across the board. It was painful, but
once done it was done.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
Dan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andrew Widdersheim [mailto:awiddersheim@hotmail.com]
<br>
<b>Sent:</b> Wednesday, January 11, 2012 7:33 PM<br>
<b>To:</b> mike-nagios@5dninja.net; nagios-devel@lists.sourceforge.net<br>
<b>Subject:</b> Re: [Nagios-devel] nsca-2.9 compatability<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">I haven't looked at NRDP much more than you have but it sounds like it would be a fix to many of NSCA's short comings. The problem for us is the
chore of switching everything over in one shot. <br>
<br>
We don't do that much passively so the check results queue feature is actually an extra bonus for us in the upgrade. We are actually more interested in the longer output. If there is an easy way to make this more compatible for with older versions than great.
If not we can plan a large upgrade 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.
<br>
<br>
-Andrew W. <o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<hr size="2" width="100%" align="center" id="stopSpelling">
</span></div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Date: Wed, 11 Jan 2012 15:38:44 -0800<br>
From: <a href="mailto:mike-nagios@5dninja.net">mike-nagios@5dninja.net</a><br>
To: <a href="mailto:nagios-devel@lists.sourceforge.net">nagios-devel@lists.sourceforge.net</a><br>
CC: <a href="mailto:awiddersheim@hotmail.com">awiddersheim@hotmail.com</a><br>
Subject: Re: [Nagios-devel] nsca-2.9 compatability<br>
<br>
On 1/11/12 11:16 AM, Andrew Widdersheim wrote: <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">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:<br>
<br>
<a href="http://tracker.nagios.org/view.php?id=78" target="_blank">http://tracker.nagios.org/view.php?id=78</a><br>
<br>
>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?
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">As far as I'm aware, there's no easy fix for this. If you cannot upgrade your clients, then you can recompile the nsca binary with MAX_PLUGINOUTPUT_LENGTH set back to 512.
That should let you use the checkresult directory feature, without breaking compatibility with older clients.<br>
<br>
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.<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Mike Lindsey<o:p></o:p></pre>
</div>
</div>
</div>
</body>
</html>