NRPE - garbage output

[Eric Aiken]

I’ve bumped into this a few times in the past.

When doing a check_nrpe to a remote server, I get additional “garbage” output that interferes with the nagios check.

I was running nrpe 2.11 and found a supposed fix in 2.12.  I’ve since upgraded both the nagios server and client to nrpe 2.12 and restarted everything with no change.

If I run the check on the client everything works as expected.  If I run it via check_nrpe it doesn’t.  The following is an example with relevant security changes:

On client:

# /usr/lib64/nagios/plugins/contrib/check_ftp.pl -H SERVERNAME -u USERNAME -p PASSWORD-f index.html
OK: Opening ASCII mode data connection for index.html(236 bytes). Transfer complete.

client nrpe.cfg entry:

command[check_ftp2web]=/usr/lib64/nagios/plugins/contrib/check_ftp.pl -H SERVERNAME -u USERNAME -p PASSWORD index.html

On server:
# check_nrpe -H SERVERNAME -c check_ftp2web 
WARNING: server says: Transfer complete.
'�ABOR': command not understood


Note the garbage and also the different result  OK vs WARNING

Any suggestions is appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090223/848496fa/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
-------------- 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