Check issues on Solaris with NRPE not dealing with ARGS

Marc Powell marc at ena.com
Wed Aug 12 16:13:50 CEST 2009


On Aug 12, 2009, at 7:54 AM, Brian O'Mahony wrote:

> [root at nagios-server servers]# /usr/local/nagios/libexec/check_nrpe - 
> H beatrix -c check_load -a 1,1,1 2,2,2
> OK - load average: 0.05, 0.05, 0.05|load1=0.051;1.000;2.000;0;  
> load5=0.051;1.000;2.000;0; load15=0.047;1.000;2.000;0;
> [root at nagios-server servers]# /usr/local/nagios/libexec/check_nrpe - 
> H beatrix -c check_procs_total -a 100 150
> PROCS OK: 66 processes
>
>
> Secondly, even though check_load works remotely, it doesn’t seem to  
> work in the nagios server tests. Here is my test entry:
> # Check CPU Load
> define service{
> use                     solaris-service-base
> hostgroup_name          solaris-base-hostgroup
> service_description     CPU Load
> check_command           check_nrpe!check_load!1,1,1!2,2,2
> #check_command           check_nrpe!check_load!15,10,5!30,25,20


> So it looks like the args are not being passed to the solaris box.

Does your check_nrpe command{} definition on the nagios box pass the  
args  the the check_nrpe program? Look for something like --

define command {
	command_name check_nrpe
	command_line $USER1$/check_nrpe (... some arguments here ...) -c  
$ARG1$ -a $ARG2$ $ARG3$
}

You might want to read http://nagios.sourceforge.net/docs/3_0/macros.html 
, Example 2.

--
Marc


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Nagios-users mailing list
Nagios-users at 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





More information about the Users mailing list