My first guess would be that there is some sort of environmental
variable being set when you log in that wouldn't be set when you
aren't (ie, when Nagios triggers it). Are you using keys that have
passphrases, maybe? Can you give us a look at the contents of
check_by_ssh?
--Matt
On Fri, Feb 5,
On Feb 5, 2010, at 9:42 AM, mirko stefanelli wrote:
> Hi,
>
> yes if I doing it from the CLI as Nagios User is work fine.
>
> Here:
>
> Command definition:
>
> # 'check_tablespace' command definition_
> define command{
> command_namecheck_tablespace
> command_line$USER
Hi,
yes if I doing it from the CLI as Nagios User is work fine.
Here:
Command definition:
# 'check_tablespace' command definition_
define command{
command_namecheck_tablespace
command_line$USER1$/check_by_ssh -H $HOSTADDRESS$ -C
"/usr/local/nagios/libexec/check_tablespac
mirko stefanelli wrote:
> Hi to all,
>
> We run nagios on Ubuntu server with 2Gb ramm kernel version
> 2.6.24-23-server. Nagios version is 3.2.0.
>
> We have configured all our server (Linux REL) to execute our custom
> plugin by check_by_ssh. The problem is that for some server this check
>
Are you able to ssh to the remote machine as the remote user? I've
been bitten by not having the remote host in my nagios user's
known_hosts file, and my scripts get prompted, and for some reason
that stops me from obtaining statistics ;-)
--Matt
On Fri, Jan 22, 2010 at 7:35 AM, Mario Rimann wr
On Fri, 22 Jan 2010 13:35:48 +0100, Mario Rimann wrote:
> Running the same stuff as the nagios user fails (script get's called,
but
> doesn't get the parameters)
> [nag...@monitoring ~]$ /path/to/libexec/check_by_ssh -l root -H
> xxx.xxx.xxx.xxx -v -C "/root/bin/checkSomeThing.sh 300 500"
Probl
