check_snmp - wrong status

[Edy Gasparini]

seems that you may have a discrepancy between what you run on the command
line vs what is defined in checkcommands.cfg
 
can you supply the service definition and the corresponding checkcommand.
i'm guessing you've messed up the ordering of the ranges (MAX:MIN vs
MIN:MAX) in checkcommands.cfg
 
Edy

-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Gÿfffff6ran
Almvik
Sent: Friday, 26 November 2004 2:06 AM
To: Nagios-users at lists.sourceforge.net
Subject: [Nagios-users] check_snmp - wrong status



Having severe problems with check_snmp in Nagios (RH 8.0). The command works
fine from command line but for unknown reasons Nagios interpretes the result
as a Warning state even if the result is within limits of both warning and
critical.
 
The command checks a temp sensor and the OID returns the temperature.
 
The command 
/usr/local/nagios/libexec/check_snmp -C public -H 10.20.29.50 -o
.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 -w 33:28 -c 100:34 -m
/root/snmp/mib_files/5.0/sp.mib
 
When run from command line the result is SNMP OK - 22. When run from Nagios
the result is SNMP Warning - 22.
 
I've tried all possible warn/crit. ranges but end up withthe same problem.
Anybody got a clue where Nagios gets this funny idea from? 
check_snmp version 1.25 (nagios-plugins 200303262200).
 
Greatful for any help!
/G 

 



  _____  

Do you Yahoo!?
The all-new My Yahoo! <http://my.yahoo.com>   Get yours free! 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20041126/31ed5e2b/attachment.html>