Red Hat Bugzilla – Bug 868191
Errata version 1.4.16 released yesterday changes behaviour in check_snmp
Last modified: 2015-09-11 10:47:54 EDT
Description of problem: My nagios box upgraded automatically from nagios-plugins-1.4.15 to nagios-plugins-1.4.16, and some behaviour has changed. Specifically... /usr/lib64/nagios/plugins/check_snmp works differently. /usr/lib64/nagios/plugins/check_snmp -c 0:149999 used to be critical if the value returned was in the range between 0 and 149999. Now, it's only critical if the range is not in 0 to 149999. I don't think errata should change behaviour, even though the new way is probably better.
Skippy, Could you check if the problem you describe has been fixed nagios-plugins 1.5 ? From the NEWS file: ---------- 1.5 2nd October 2013 ENHANCEMENTS ... New check_snmp --offset option to allow for adding/substracting an offset value to sensor data Let check_snmp support an arbitrary number of OIDs ... FIXES ... Fix check_snmp reversed threshold ranges (backward-compatibility) Fix check_snmp memory violation when using more than 8 oids (Robin Sonefors) ... ---------- Source: https://www.nagios-plugins.org/doc/news.txt
The Nagios Plugin guidelines state this is expected behavior https://nagios-plugins.org/doc/guidelines.html#THRESHOLDFORMAT Additionally the version mentioned in this bug is no longer being used.