check_by_ssh problem

[Anirudh Srinivasan]

In order to monitor the remote linux server we are using check_by_ssh as
root. I know it is not advisable to use it as root , but we are in a
transition to NRPE slowly which uses nagios.

Here's what i did :

1) As root copied the id_rsa.pub to the remote server's  root user's .ssh
directory and pasted it to the authorized_keys .

2) Then did ssh <remote server ip> and was able to login without password.

3) Then excecuted the check command remotely:

check_by_ssh -t 30 -l root -H <remote server ip> -C
"/usr/lib/nagios/plugins/check_load -w10,15,20 -c15,20,25"
OK - load average: 0.00, 0.00,
0.00|load1=0.000000;10.000000;15.000000;0.000000
load5=0.000000;15.000000;20.000000;0.000000
load15=0.000000;20.000000;25.000000;0.000000

check_by_ssh -t 30 -l root -H <remote server ip>  -C
"/usr/lib/nagios/plugins/check_uptime"
UPTIME OK - System up for 6 HOUR(s) and 38 Minute(s)
 Looks perfectly fine!!!

But from the Web interface i see this :

Remote command execution failed: buffer_get_ret: trying to get more bytes
129 than in buffer 97

I am clue less . Please advice me on this .
-- 
Anirudh Srinivasan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090508/3c9f27c1/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
-------------- 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