If I want to set Nagios distribution architecture, can I still use check_by_ssh
with NSCA server?
eg.
Nagios central server <--> NSCA ---execute ssh--> host 1
in this sense, NSCA will gather information from host 1 using check_by_ssh, and
send back the collected data to the Nagios central server.
Is this possible? how to setup the monitoring architecture like this?
Links, reference/guides are most welcome.
Thanks
Sam
----- Original Message ----
From: Live Great <[EMAIL PROTECTED]>
To: nagios-users@lists.sourceforge.net
Sent: Wednesday, October 3, 2007 4:22:48 PM
Subject: Re: check_by_ssh - please clarify.
Hi,
This is the follow up the previous question.
For example, if I want to check disk info in a remote host,
In the NSCA server, I will define the following config:
define command{
command_name check_slash_free
command_line $USER1$/check_by_ssh -i /var/ssh/nagios-key -l root -H
$HOSTADDRESS$ -C '$USER1$/check_disk -w $ARG1$ -c $ARG2$ -p /'
}Do I only need to install check_disk script/program in the remote host
without installing nagios and other nagios plugins?
Thanks[
Sam
----- Original Message ----
From: Live Great <[EMAIL PROTECTED]>
To:
nagios-users@lists.sourceforge.net; nagios-users@lists.sourceforge.net
Sent: Wednesday, October 3, 2007 4:14:25 PM
Subject: check_by_ssh - please clarify.
Hi,
I am aware that NSCA can uses check_by_ssh to check remote host.
I am wondering if this means I don't have to install NSCA or Nagios plugins in
remote host?
Thanks
Sam
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
