NSClient++ and CheckEventLog

Klaus Umbach treibholz at sozial-inkompetent.de
Mon Jan 19 12:11:32 CET 2009


On 19/01/09 11:07, Michael Medin wrote:
> It has nothing to do with language...
>
> The reason is that one of them has an entry which is "too long" so you  
> need to update the buffer used when NSClinet++ reads the eventlog.
> The simplest way to solve this is to increase the buffer_size variable  
> to something "large enough".
> If you check the wiki/forums on nsclient.org you can find some "values  
> that worked for others" or you can play around and find what works for 
> you.

Thanks!

buffer_size=520000 worked. Now I have to change it everywhere... :-(

- Klaus

>
> // Michael Medin
>
> Klaus Umbach skrev:
>> Hi,
>>
>> I wonder why the following check works on a German Windows 2k3 server, but
>> not on an English one. To me this makes no sense... NSC.ini is the same.
>>
>> CheckEventLog filter=new file=application MaxWarn=1 MaxCrit=1 filter+generated=<2h filter==eventID=888
>>
>> Errormessage: "EventlogBuffer is too small (set the value of buffer_size): 122 The data area passed to a system call is too small."
>>
>> NSClient++ Version: 0.3.5.1 2008-09-24 (32bit)
>>
>> Maybe the language is just a coincidence...
>>
>> Cheers
>>         Klaus
>>
>>
>>   
>
>

-- 
BOFH excuse #271:

The kernel license has expired

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list