Page 1 of 1

255 Exit status from Solaris 9 servers

Posted: Mon Feb 28, 2011 12:02 pm
by GBarlow
Hi Nagios Forum,

I'm monitoring 70 odd Solaris 9 servers and 13 of them return 255 error codes when Nagios performs check_by_ssh checks. The check works fine if I perform it on the remote machine and if I run the command directly from the Nagios machine. But put it in Nagios and it gives me the 255 error code 9 times out of 10.

The command I'm running is:

/usr/local/groundwork/nagios/libexec/check_by_ssh -H <Remote IP> -t 120 -l "nagios" -q -C "./libexec/check_disk -w 10% -c 5% -p /opt"

Output from the Nagios machine is

DISK OK - free space: /opt 5294 MB (88%);| /opt=755MB;5443;5745;0;6048
$ echo $?
0

However in Nagios I get the following output:

/usr/local/groundwork/nagios/libexec/check_by_ssh -H <Remote IP> -t 120 -l "nagios" -q -C "./libexec/check_disk -w 10% -c 5% -p /opt"
DISK OK - free space: /opt 5321 MB (88%);| /opt=727MB;5443;5745;0;6048

Command returned exit status 255

The Command is defined as:

define command {
command_name check_by_ssh_disk
command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -t 120 -l "$USER17$" -q -C "$USER22$/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$"
}

All of our hosts are defined as:

define host {
host_name <hostname>
alias <hostname>
address <Remote IP>
use generic-host
}


As I've said, this same check works fine on most of my Solaris 9 machines. If any of you have any information that could help me in rectifying this issue I would be very grateful

Kind regards

Re: 255 Exit status from Solaris 9 servers

Posted: Tue Mar 01, 2011 11:42 am
by tonyyarusso
If you're using GroundWork, you should be seeking support from GroundWork channels.

Re: 255 Exit status from Solaris 9 servers

Posted: Thu Mar 03, 2011 9:12 am
by sun-support
hello.can you give me a document that nagios install to solaris 10 !
mail:wangshuangyi@yahoo.cn
thank you !

Re: 255 Exit status from Solaris 9 servers

Posted: Tue Mar 08, 2011 11:39 am
by GBarlow
Hi,

Groundwork is just used as a front end. All the monitoring is done through Nagios. Is there anything that anyone can think of to rectify this error?

Cheers

GBarlow