I installed the snmptt script in daemon mode (http://www.snmptt.org/docs/snmptt.shtml), and set snmptt to call submit_check_result upon the receipt of an unknown trap. The above link should tell you how to set it up in a couple of minutes, and I've included my snmptt.ini file.
It just occurred to me that perhaps I've filed this bug in the wrong place. Maybe this is a bug with snmptt? I'm not sure. All I know that snmptt launches submit_check_result now, but it didn't before.
I installed the snmptt script in daemon mode (http:// www.snmptt. org/docs/ snmptt. shtml), and set snmptt to call submit_check_result upon the receipt of an unknown trap. The above link should tell you how to set it up in a couple of minutes, and I've included my snmptt.ini file.
When snmptt receives an unknown trap, it should launch submit_ check_result, but without the change (which I found recommended here: http:// forums. meulie. net/viewtopic. php?f=59& t=4342& p=15475& hilit=snmptt# p15475 ) it does nothing, and I can't seem to find any errors in the log files explaining why.
It just occurred to me that perhaps I've filed this bug in the wrong place. Maybe this is a bug with snmptt? I'm not sure. All I know that snmptt launches submit_check_result now, but it didn't before.