Running nagios 3.0.6 on OpenSUSE and trying to get info from a SUSE enterprise
machine.
Chk_by_ssh returns UNKNOWN and "Remote command execution failed: Host key
verification failed", check_ping works.
I have played with every combo of options I could think of, but same results.
This is my first setup with remote checks on a linux machine (windows machine
checks working fine), so it could be a newb problem.
(from commands.cfg)
# check_ssh_dummy command definition
define command{
command_name check_ssh_dummy
command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -l nagios -2 \
-I /etc/nagios/.ssh/id_dsa -C "/usr/lib/nagios/plugins/check_dummy 0"
}
I took out the desired response text to eliminate possible double quote issues,
but it made no difference
(from object config)
define service{
use local-service
host_name (machine_name)
service_description PING
check_command check_ping!100.0,20%!500.o,60%
}
define_service{
use local-service
host_name (machine_name)
service_description check_ssh_dummy!
}
>From the command line, I run:
/usr/lib/nagios/plugins/check_by_ssh -H (machine_ip) -l nagios -i
/etc/nagios.ssh/id_dsa -C "usr/lib/nagios/plugins/check_dummy 0"
It returns OK
I am having the same issue with check_ssh_disk. I do not have a MOTD for the
shell, I have tried putting explicit paths in place of USER1, putting in the
actual address for HOSTADDRESS, and many options on the
Robert L. O'Donnell
Advanced Equipment Engineering, IMO
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Nagios-users mailing list
Nagios-users@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
