from snmptt site:niobe wrote:Hi gthe,
I created a few different .conf files use MIB packs from different vendors. Since these are not perfect and some re-include the standard RFC MIBS no doubt there are duplicates.
Is there a way for snmptt to find and avoid these duplicates itself?
Code: Select all
Q: Each trap received is being logged multiple times. Why?
A: There are a few possible reasons for this.
* The device is sending the trap multiple times. If the device is running Net-SNMP's agent (snmpd), make sure there is only ONE trapsink, trap2sink or informsink line in snmpd.conf. If you are sending the trap using SNMP V1, use trapsink. For SNMP V2, use trap2sink. For SNMP V3, use informsink. Having both a trapsink and a trap2sink for example will cause snmpd to send the trap twice. Once using SNMP V1 and once using SNMP V2. It is possible that snmpd is loading multiple snmp.conf files. Start snmpd using snmpd -f -Dread_config to see what configuration files are being loaded.
* Snmptrapd is passing the trap to SNMPTT multiple times. Ensure there is only one traphandle statement in snmptrapd.conf. It is possible that snmpdtrapd is loading multiple snmptrapd.conf files. Start snmpdtrapd using snmpd -f -Dread_config to see what configuration files are being loaded.
* There is more than one EVENT line defined in one or more snmptt.conf files for the trap and multiple_event is enabled in snmptt.ini. To find all duplicate EVENT entries, run snmptt --dump
Do you have new rows in mysqld_slow.log with new (0.1.22b) version ?niobe wrote: But I think even half as many traps coming in is still quite a few, so performance could still be a concern.