<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hello,<br>
<br>
It should already be in NSClient++don't really use it myself so let
me know if it doesn't work...<br>
<br>
// Michael Medin<br>
<br>
2011-04-01 14:38 Ton Voon skrev:
<blockquote
cite="mid:588B712E-76A6-4A86-AC0D-C941F5E6CEC7@gmail.com"
type="cite"><br>
<div>
<div>On 29 Mar 2011, at 17:08, Daniel Wittenberg wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
font-size: medium;">
<div><font face="Calibri" size="2"><span style="font-size:
11pt;">
<div>I’ve seen this problem posted from many sources
over the years, but alas, there is no way to
dynamically adjust the NRPE buffers in the main
code.</div>
<div> </div>
<div>I updated nrpe-2.12/include/common.h:</div>
<div> </div>
<div>#define MAX_INPUT_BUFFER 20480</div>
<div><font face="Times New Roman"> </font></div>
<div>#define MAX_PACKETBUFFER_LENGTH 20480</div>
<div><font face="Times New Roman"> </font></div>
<div>I can then use check_nrpe to talk to our
nslclient (with string_length=20480) and everything
appears to work fine. However, when talking to
nrpe, even localhost, I still get some CRC failure
messages. For the heck of it I disabled that fatal
return code, and sometimes it works, sometimes it
doesn’t. Any clue why crc would sometimes fail and
sometimes not ? I looked at the code but didn’t see
anything obvious. There was a nice patch from op5
for nrpe:</div>
<div> </div>
<div><font face="Times New Roman"><a
moz-do-not-send="true"
href="http://labs.opsview.com/2008/08/enhancing-nrpe-for-large-output/"><font
color="blue" face="Calibri"><u>http://labs.opsview.com/2008/08/enhancing-nrpe-for-large-output/</u></font></a></font></div>
</span></font></div>
</span></blockquote>
<div><br>
</div>
*Ahem*. Opsview, not op5 :)</div>
<div><br>
</div>
<div>
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
font-size: medium;">
<div><font face="Calibri" size="2"><span style="font-size:
11pt;">
<div>But there’s no patch for nsclient to do this and
since I have multi-platforms to support that doesn’t
work so well for me. Any other clues how to get
this to work stable with larger buffer sizes?</div>
</span></font></div>
</span></blockquote>
<div><br>
</div>
You would have to patch nsclient++ to include this. Michael
Medin is the developer and I'm sure he'd welcome a working
example.</div>
<div><br>
</div>
<div>Ton</div>
<div><br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/ms-webmatrix-sf">http://p.sf.net/sfu/ms-webmatrix-sf</a>
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________________
Nagios Plugin Development Mailing List <a class="moz-txt-link-abbreviated" href="mailto:Nagiosplug-devel@lists.sourceforge.net">Nagiosplug-devel@lists.sourceforge.net</a>
Unsubscribe at <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a>
::: Please include plugins version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null</pre>
</blockquote>
<br>
</body>
</html>