[ nagiosplug-Bugs-3585441 ] snmp_check -C parsing error

Bugs item #3585441, was opened at 2012-11-08 10:32
Message generated for change (Comment added) made by j-bern
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3585441&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Parsing problem
Group: Release (specify)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Leandro Toledo de Souza (leandrotoledo)
Assigned to: Nobody/Anonymous (nobody)
Summary: snmp_check -C parsing error

Initial Comment:
Hi there,
I'm having some issues with release v1.4.16 when using check_snmp with -C arg.

See above:
- In check_snmp (nagios-plugins 1.4.16) v1.4.16:
# ./check_snmp -C border -H 10.10.0.6 -o iso.3.6.1.2.1.2.2.1.9.3 -v 
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 [authpriv] 10.10.0.6:161 iso.3.6.1.2.1.2.2.1.9.3
(Service Check Timed Out) 

- In check_snmp (nagios-plugins 1.3.1) v1.24.2.2:
# ./check_snmp -C border -H 10.10.0.6 -o iso.3.6.1.2.1.2.2.1.9.3 -v
/usr/bin/snmpget -t 1 -r 9 -m ALL -v 1 -c border 10.10.0.6:161  iso.3.6.1.2.1.2.2.1.9.3
RFC1213-MIB::ifLastChange.3 = Timeticks: (362154105) 41 days, 21:59:01.05
SNMP OK - Timeticks: (362154105) 41 days, 21:59:01.05

It seems that the -C (--community too) argument was not treated.

OS/Arch: Linux nagios3teste 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 GNU/Linux
Compiler: gcc version 4.4.5 (Debian 4.4.5-8)

----------------------------------------------------------------------

Comment By: J. Bern (j-bern)
Date: 2012-11-09 00:29

Message:
I can *not* confirm that this is a general problem with this plugin version
...

[root@nagios ~]# nagios-plugins-1.4.16/plugins/check_snmp -C public -H
$TARGET -o sysUpTime.0 -v
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 [authpriv] $TARGET:161 sysUpTime.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1356951290) 157 days,
1:18:32.90
SNMP OK - Timeticks: (1356951290) 157 days, 1:18:32.90 |

[root@nagios ~]# nagios-plugins-1.4.16/plugins/check_snmp -C wrong -H
$TARGET -o sysUpTime.0 -v
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 [authpriv] $TARGET:161 sysUpTime.0
External command error: Timeout: No Response from $TARGET:161.

The community being hidden in the command line (as "ps" sees it) is a
safety mechanism of snmpget itself:

[root@nagios ~]# nagios-plugins-1.4.16/plugins/check_snmp -C wrong -H
$TARGET -o sysUpTime.0 -v &
[...]
[root@nagios ~]# ps auwwwwx | grep snmpget
root     22907  0.0  0.1   4364  1856 pts/1    S    09:17   0:00
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 -c       $TARGET:161 sysUpTime.0

Source retrieved 28-Jun, md5sum is:
862f5e44fb5bc65ce7e5d86d654d4da0  nagios-plugins-1.4.16.tar.gz

You might want to rerun the tests with numeric-only OIDs, to make sure that
the timeout isn't due to the MIB file parsing.

----------------------------------------------------------------------

Comment By: Leandro Toledo de Souza (leandrotoledo)
Date: 2012-11-08 11:04

Message:
After read the source I saw the verbose message above only show some args.

Full command above (through pid info):
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 -c        200.196.193.25:161
iso.3.6.1.2.1.2.2.1.9.3

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3585441&group_id=29880

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________________
Nagios Plugin Development Mailing List Nagiosplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null