Disregard. Found the problem.
"The purpose of life is not to be happy. It is to be useful, to be honorable,
to be compassionate, to have it make some difference that you have lived and
lived well". (Ralph Waldo Emerson)
________________________________
From: Chris Bartram <chrisrbart...@yahoo.com>
To: net-snmp-users@lists.sourceforge.net
Sent: Fri, November 12, 2010 2:56:26 PM
Subject: traphandle not firing for some traps
Hello,
I'm running NET-SNMP version 5.4.1
on Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 GNU/Linux
Have a relatively large snmptrapd.conf file listing multiple trap handlers.
MOST
are working fine. Some don't seem to fire off their scripts at all. All my trap
handling scripts write a message to a log file as soon as they're kicked off
(before reading anything) so I can tell if they're getting triggered.
I can see in my /var/log/messages that the traps ARE coming in; and they're
being parsed correctly. I enabled the logOption in snmptrapd.conf as well and
can see in that file the trap contents - yet no sign they're firing off the
trap
handler scripts.
I attached a copy of my snmptrapd.conf (note I also tried adding traphandle
statement with numeric OIDs in case that helped; it doesn't). I can run all the
scripts manually (either as the creator or as root) and they work fine; in
particular the first thing they do is write to that log file - which I never
see
for the problematic SUN and Oracle traps.
I've attached a copy of the snmpdebug file as well so you can see examples of
what came in during one interval. Note that all the EMC/EMC-RecoverPoint traps
come in and fire off their scripts just fine - even though the Recoverpoint
traps have mib data issues (some embedded binary data due to MIB issues). In
particular the Sun-HW traps and the Oracle CELL-ALERT traps are not firing off
their respective scripts at ALL. Have stopped/restarted SNMP several times; no
errors or warnings displayed. The trap identifiers in the snmptrapd.conf match
exactly the names that show up in the /var/log/messages and snmpdebug file.
I've got extracts from the var/log/messages logged data as well. Nothing seems
odd about these traps. They're all SNMPv1 and all use the "public" community
string; so I'm at a loss as to why some fire and some don't.
I even tried firing up NET-SNMP with debugging enabled.. unfortunately the
volume of "stuff" filling up the logs caused me to shut that off before I saw
anything meaningful/helpful.
Did I miss something simple??
Thanks in advance!
-Chris Bartram
"The purpose of life is not to be happy. It is to be useful, to be honorable,
to be compassionate, to have it make some difference that you have lived and
lived well". (Ralph Waldo Emerson)
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
