After update to 5.7 using snmp will cause some "cannot find module" noise, for examle: > snmpget -v2c -c public localhost SNMPv2-MIB::sysDescr.0 MIB search path: /home/cgenybr/.snmp/mibs:/usr/local/share/snmp/mibs Cannot find module (SNMPv2-SMI): At line 6 in /usr/local/share/snmp/mibs/SCTP-MIB.txt Cannot find module (SNMPv2-TC): At line 8 in /usr/local/share/snmp/mibs/SCTP-MIB.txt Cannot find module (INET-ADDRESS-MIB): At line 12 in /usr/local/share/snmp/mibs/SCTP-MIB.txt Cannot find module (SCTP-MIB): At line 1 in (none) Cannot find module (SNMPv2-MIB): At line 1 in (none) Cannot find module (IANAifType-MIB): At line 13 in /usr/local/share/snmp/mibs/IF-MIB.txt Cannot find module (IF-MIB): At line 1 in (none) Cannot find module (IP-MIB): At line 1 in (none) Cannot find module (TCP-MIB): At line 1 in (none) Cannot find module (UDP-MIB): At line 1 in (none) Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none) Cannot find module (SNMP-FRAMEWORK-MIB): At line 11 in /usr/local/share/snmp/mibs/NOTIFICATION-LOG-MIB.txt Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none) Cannot find module (SNMP-TARGET-MIB): At line 14 in /usr/local/share/snmp/mibs/DISMAN-EVENT-MIB.txt Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none) Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none) Cannot find module (UCD-SNMP-MIB): At line 1 in (none) Cannot find module (UCD-DEMO-MIB): At line 1 in (none) Cannot find module (NET-SNMP-MIB): At line 12 in /usr/local/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt Cannot find module (NET-SNMP-AGENT-MIB): At line 1 in (none) Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none) Cannot find module (SNMP-MPD-MIB): At line 1 in (none) Cannot find module (SNMP-USER-BASED-SM-MIB): At line 1 in (none) Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 1 in (none) Cannot find module (SNMP-COMMUNITY-MIB): At line 1 in (none) Cannot find module (NET-SNMP-EXAMPLES-MIB): At line 11 in /usr/local/share/snmp/mibs/NET-SNMP-PASS-MIB.txt Cannot find module (NET-SNMP-PASS-MIB): At line 1 in (none) Cannot find module (NET-SNMP-EXTEND-MIB): At line 1 in (none) Cannot find module (UCD-DLMOD-MIB): At line 1 in (none) Cannot find module (SNMP-NOTIFICATION-MIB): At line 1 in (none) Cannot find module (SNMPv2-TM): At line 1 in (none) Cannot find module (NET-SNMP-VACM-MIB): At line 1 in (none) SNMPv2-MIB::sysDescr.0 = STRING: shevdid.com 4266707402 FreeBSD 7.4-RELEASE Problem discussion here: http://www.mail-archive.com/net-snmp-users@lists.sourceforge.net/msg28230.html Patch and description found here: http://sourceforge.net/tracker/?func=detail&aid=3362233&group_id=12694&atid=312694 (copied details) In 5.5, the behavior when starting up snmpd, doing a walk, etc was less noisy than in 5.7. This is due to a side effect introduced via r20472 -- in particular the fact that there are some SMIs like SNMPv2-SMI return NULL via parse (this is wrong given the definition of this MIB file, but everything works later on when doing an snmp operation with the MIBs specified). So instead of falling back to MODULE_NOT_FOUND in read_module_internal, the following returns an appropriate value according to gMibError, and also extends gMibError to cover error cases in parse. Later on things should ultimately be cleaned up so that the silent 'parsing' error is properly resolved in the SMI, whether it be by redefining the SMI to include all of the necessary symbols or a proper code change to accommodate the parsing discrepancies in the file. Fix: Patch attached with submission follows: How-To-Repeat: update to net-snmp 5.7 and run > snmpget -v2c -c public localhost SNMPv2-MIB::sysDescr.0
Responsible Changed From-To: freebsd-ports-bugs->sylvio Over to maintainer (via the GNATS Auto Assign Tool)
Problem discussion here: http://www.mail-archive.com/net-snmp-users@lists.sourceforge.net/msg28230.html Patch and description found here: http://sourceforge.net/tracker/?func=detail&aid=3362233&group_id=12694&atid=312694 (copied details) In 5.5, the behavior when starting up snmpd, doing a walk, etc was less noisy than in 5.7. This is due to a side effect introduced via r20472 -- in particular the fact that there are some SMIs like SNMPv2-SMI return NULL via parse (this is wrong given the definition of this MIB file, but everything works later on when doing an snmp operation with the MIBs specified). So instead of falling back to MODULE_NOT_FOUND in read_module_internal, the following returns an appropriate value according to gMibError, and also extends gMibError to cover error cases in parse. Later on things should ultimately be cleaned up so that the silent 'parsing' error is properly resolved in the SMI, whether it be by redefining the SMI to include all of the necessary symbols or a proper code change to accommodate the parsing discrepancies in the file. >How-To-Repeat: update to net-snmp 5.7 and run # snmpget -v2c -c public localhost SNMPv2-MIB::sysDescr.0
State Changed From-To: open->closed Committed. Thanks!