NRPE Character limitation

[Mohr James]

Hi All!

We have run into the infamous 350 character nrpe boundary. I have done a
a lot of research on what the problem is, but what I am missing is
*where* the problem is. What I have been able to find out is that the
problem lies in the limit of an atomic write to a pipe and therefore the
nrpe code has been configure to limit the size of messages. The question
is where in the chain is this pipe? 

I found the my_system function in nrpe.c where it uses a pipe. However,
shouldn't this pipe be unique to the process? If so, then this shouldn't
be the place where there is a problem, or is it? Looking through the
code just within the nagios base directory, there are a number of places
where various pipes are used, so I am having trouble finding the exact
spot.

The bottom line is we want/need to return larger amounts of data. Thus,
I need to find the place(s) where I should change the code, as well as
the place(s) where there are problems. I cannot find within the nrpe
code, where this limit is defined. We have called check_nrpe directly,
avoiding Nagios completely and we still have this limitation, so it
seems that the limit is either in check_nrpe or nrpe itself. Thus, I
cannot find where I need to increase this value. 

If the problem really is within Nagios, is it possible to use the Nagios
Event Broker to catch the messages, write the complete text to a file
and then cut the message down to the 350 character limit? 

Any help is greatly appreaciated.

Regards,

Jim Mohr


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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