Hi list, I have some issues with the plugin "check_by_ssh". In particular, there is one error:
When I run a shell script located in another server, from the Nagios server
using the check_by_ssh plugin, I don't have any errors and I can see the
result of the script, like this:
*root@nagioserver# <root@TSM-SRV-V-114#> /usr/lib/nagios/plugins/check_by_ssh
-l root -H "ipxenserver" -C /usr/lib/nagios/plugins/check_Xencpu
“OK:CPU%= 3”*
*
*
But, by any strange reason, when I configure the check for Nagios presents
the results in its interface, I have the error:
[image: Imágenes integradas 1]
I have made the ssh authorization keys in both servers (Nagios and Xen), I
configured the users, permissions,etc. And I can't to do this work it.
Could someone help me solve this problem????
This is a part of my definition files:
*
#XENServer
*
*
define command {
command_name check_by_ssh_xentop
command_line /usr/lib/nagios/plugins/check_by_ssh -l
'$ARG1$' -H '$HOSTADDRESS$' -C '$ARG2$' -i '$ARG3$'
}
*
*#Hypervisor check*
* define service{*
* use generic-service*
* host_name ORLANDO *
* service_description Hypervisor CPU*
* check_command
check_by_ssh_xentop!root!ipxenserver!/usr/lib/nagios/plugins/check_Xencpu.sh!/root/.ssh/id_rsa!
*
* }*
Regards!
--
*IC.** Eduardo Montes de Oca Sánchez
*Skype: edrendar
Gmail: edren...@gmail.com
MSN: ed_montesde...@hotmail.com
Movil: 5523419886
https://linuxcounter.net/cert/549074.png
<<image.png>>
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ 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
