Hi Tibor,
This is a very long-standing net-snmp bug, and doesn't really have anything to do with us. net-snmp seems to generate corrupted .index files occasionally, and then chokes on loading mibs from directories containing these files.
If you remove the .index file, net-snmp will generate an uncorrupted one and everything should work again.
Thanks, adam. On 11/02/2016 11:32:04, Tibor Marchyn tibor.marchyn@zoomint.com wrote: Hi,
From yesterday, my observium poller stopped working. I have paid observium and probably something happened in source daily updates.
Output from debug is below. When I do snmpget from observium server manually without “-M” option I get values correctly. Anybody have the same problem? Thanks ##### DEBUG ##### CMD[/usr/bin/snmpget -v2c -c public -Pu -OQUst -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'sw-show-01.domain.com':'161' sysObjectID.0 sysUpTime.0] EXITCODE[1] CMD RUNTIME[0.0076s] STDOUT[ ] STDERR[ add_mibdir: strings scanned in from /opt/observium/mibs/rfc/.index are too large. count = 133 MIB search path: /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp Cannot find module (SNMPv2-MIB): At line 0 in (none) sysObjectID.0: Unknown Object Identifier (Sub-id not found: (top) -> sysObjectID) sysUpTime.0: Unknown Object Identifier (Sub-id not found: (top) -> sysUpTime) ] SNMP_STATUS[FALSE] o Device status Device is not responding to SNMP requests ##### MANUAL RUN ##### [root@observium tmp]# /usr/bin/snmpget -v2c -c public -Pu -OQUst -m SNMPv2-MIB sw-show-01.domain.com:161 sysObjectID.0 sysUpTime.0 sysObjectID.0 = enterprises.9.1.516 sysUpTime.0 = 700180848