check_by_ssh not working

[Nelson Serafica]

	Here's the scenario:

user John can connect via ssh to SONICSERVER using oracle user without authentication. To verify, i run this command and encountered no problem:

ssh -i /home/John/.ssh/id_rsa oracle at SONICSERVER w

and the commands run properly.

But when i tried this command: 

[John at SONICSERVER ~]$ /usr/local/nagios/libexec/check_by_ssh -H SONICSERVER -i /home/John/.ssh/id_rsa \
 -C "/usr/local/nagios/libexec/check_disk -w 10% -c 5% -e -m" -l oracle

It says: 

CRITICAL - Plugin timed out while executing system call

By the way, I also tried :

/usr/local/nagios/libexec/check_by_ssh -H SONICSERVER -i /home/oracle/.ssh/authorized_keys -C '/usr/local/nagios/libexec/check_swap -w 50% -c 10%' -l oracle

but encounter the same error: 

CRITICAL - Plugin timed out while executing system call

Is there something wrong in the command??? Plugins was own by nagios but i set permission that John can execute it as well.
 
 I just notice that most people that uses nagios monitoring via ssh uses dsa not rsa. Is there a diffrence between dsa and rsa when using it to nagios??


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060824/1d56e2dc/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- 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