Odd problem with check_snmp

[Dave Alden]

Hi,
  I'm having problems with a check_snmp command.  I'm trying to setup a
service which will warn me if the load goes over 2.  The problem is that
it seams to consider anything over 1 as a WARNING state.  If I run the
command by hand, it does the "proper" thing (only sets WARNING if the
load is over 2).  To make sure that I'm running the same command, I setup
a second service and command that echo the command to a dummy file -- it
is exactly what I would expect.  If I then source the dummy file, I get
back the proper answer (if the load is below 2, the state is "OK").
Any suggestions or pointers?
...thnx,
...dave

ps  The service and command entries are:

define service{
  use                  template-service-snmp-load
  host_name            mathserv
  check_command        check-snmp-load!somepass!:200!:300
  }

define service{
  use                  template-service-snmp-load
  service-description  snmp load fubar
  host_name            mathserv
  check_command        check-snmp-load2!somepass!:200!:300
  }

define command{
  command_name         check-snmp-load
  command_line         $USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o .1.3.6.1.4.1.2021.10.1.5.1 -w $ARG2$ -c $ARG3$ -l load
  }

define command{
  command_name         check-snmp-load2
  command_line         echo $USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o .1.3.6.1.4.1.2021.10.1.5.1 -w $ARG2$ -c $ARG3$ -l load > /tmp/fubar
  }



-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
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