passive service check where display_name larger then 128 characters

[Paul Vaes]

Hello,

The issue is that if I define a nagios service where the service description
is larger than 128 characters, everything seem to work properly except that
running a script which sends a passive service check via send_nsca the
service in the Nagius gui is not updated although the send_nsca says it was
successfully sent. Looking in the nagios log, I see that the passive check
is arrived but that the service description is chopped at 128 chars.

I wonder if anyone fixed this problem already? It looks to me that following
line in include/common.h causes the issue
#define MAX_DESCRIPTION_LENGTH    128

I assume that I need to recompile nsca ( for the server ) and send_nsca (
for the client where I need to use a service description longer then 128).
The problem is that as soon as I will use the new nsca binary on the server,
I expect problems with all the servers which still are using the original
send_ncsa.

Anybody any idea's, suggestions or solutions.

I am using the latest nsca and send_nsca 2.7.2
nsca is running on SUSE 10.2
send_nsca on different Unix and Linux falvours


Thanks in advance,

-- 
Groetjes,

Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090609/0d9a568b/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
-------------- next part --------------
_______________________________________________
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