Hi, Boratsorry to bother you again, i've find your post. http://lists.lm-sensors.org/pipermail/lm-sensors/2010-May/028535.htmlYes, I got the same error when I upgraded our Debian unstable systems to snmp 5.4.2.1 (libsnmp-base 5.4.2.1). I filed a (similar) bug with the package maintainer (581007), please see: So I rolled my packages back to 5.4.1~dfsg-12 (snmp, snmpd, libsnmp-base) and will keep them there until they sort this out. I suggest you ask the net-snmp list to fix this problem. The MIB that the lm-sensors people provide is clean and minimal; although there's room for improvement, I believe it is not their problem that net-snmp broke this functionality aspect. Or maybe they're in the process of fixing it already? (Someone correct me if I'm wrong) Here are relevant SNMP configuration parameters that work with package versions I mentioned above: root@client:~# cat /etc/snmp/snmpd.conf # lines with v2c / v3 security stuff ... # give access to sensors tree view systemview included .1.3.6.1.4.1.2021.13.16 root@client:~# cat /etc/sensors.conf # proper per your motherboard Daemons running: snmpd, sensord (optional) root@nms-server:~# # snmpbulkwalk -v2c -cpublic client LM-SENSORS-MIB::lmTempSensorsTable LM-SENSORS-MIB::lmTempSensorsIndex.1 = INTEGER: 0 LM-SENSORS-MIB::lmTempSensorsIndex.2 = INTEGER: 1 LM-SENSORS-MIB::lmTempSensorsIndex.3 = INTEGER: 2 LM-SENSORS-MIB::lmTempSensorsIndex.4 = INTEGER: 3 LM-SENSORS-MIB::lmTempSensorsIndex.5 = INTEGER: 4 LM-SENSORS-MIB::lmTempSensorsDevice.1 = STRING: CPU0 Temp LM-SENSORS-MIB::lmTempSensorsDevice.2 = STRING: CPU1 Temp LM-SENSORS-MIB::lmTempSensorsDevice.3 = STRING: temp3 LM-SENSORS-MIB::lmTempSensorsDevice.4 = STRING: temp4 LM-SENSORS-MIB::lmTempSensorsDevice.5 = STRING: MB Temp LM-SENSORS-MIB::lmTempSensorsValue.1 = Gauge32: 55000 LM-SENSORS-MIB::lmTempSensorsValue.2 = Gauge32: 58000 LM-SENSORS-MIB::lmTempSensorsValue.3 = Gauge32: 4294839296 LM-SENSORS-MIB::lmTempSensorsValue.4 = Gauge32: 4294839296 LM-SENSORS-MIB::lmTempSensorsValue.5 = Gauge32: 32000 One thing I noticed is that the walk returns parameters (and bogus values) I explicitly set to 'ignore' in my sensors.conf. I'd love it if it wouldn't: root@client:~# grep ignore /etc/sensors.conf ignore in3 ignore temp3 ignore temp4 ignore fan7 ignore fan8 ignore fan9 ignore fan10 You can then build a grep script that gives you [param]:[value] pairs and dump them in an rrd file. Best, Virgil |
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
