Page 1 of 1

weird snmptt issue

Posted: Mon Dec 09, 2013 3:13 pm
by benhank
hey when I run

Code: Select all

service snmptt restart
a buch of this comes out:

Code: Select all

,This notification is a generic notification intended for direct user $*,
Event: .1.3.6.1.4.1.476.1.42.3.7.8.2 => lgpSysNormal,Status Events,Normal,The system has returned to a normal operating state. This implies $*,
Event: .1.3.6.1.4.1.8072.2.3.0.1 => netSnmpExampleHeartbeatNotification,Status Events,Normal,An example notification, used to illustrate the $*,
Event: .1.3.6.1.4.1.8072.4.0.1 => nsNotifyStart,Status Events,Normal,An indication that the agent has started running. $*,
Event: .1.3.6.1.4.1.8072.4.0.2 => nsNotifyShutdown,Status Events,Normal,An indication that the agent is in the process of being shut down. $*,
Event: .1.3.6.1.4.1.8072.4.0.3 => nsNotifyRestart,Status Events,Normal,An indication that the agent has been restarted. $*,
Event: .1.3.6.1.6.3.1.1.5.1 => coldStart,Status Events,Normal,A coldStart trap signifies that the SNMP entity, $*,
Event: .1.3.6.1.6.3.1.1.5.2 => warmStart,Status Events,Normal,A warmStart trap signifies that the SNMP entity, $*,
Event: .1.3.6.1.6.3.1.1.5.3 => linkDown,Status Events,Normal,A linkDown trap signifies that the SNMP entity, acting in $*,
Event: .1.3.6.1.6.3.1.1.5.4 => linkUp,Status Events,Normal,A linkUp trap signifies that the SNMP entity, acting in an $*,
Event: .1.3.6.1.6.3.1.1.5.5 => authenticationFailure,Status Events,Normal,An authenticationFailure trap signifies that the SNMP $*,

Finished printing out all events in hash table
==========================================================
cwd: /
                                                           [  OK  ]
what gives?

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 3:24 pm
by abrist
Someone correct me if I am wrong, but those are cached events getting handled. . . .

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 4:21 pm
by benhank
so vas ist dast meen?
whatcho talkin bout willis?

is ther a way tah clear the cache?

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 4:30 pm
by abrist
I am talkin' bout the traps Gary.
Does it happen every time you restart the service?

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 4:43 pm
by benhank
yeah, but i think this is from a a bad conversion of my mibs
the devices it's showing have never been monitored or cfg'd to send traps to this system.

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 4:49 pm
by abrist
Ahhh. Are you using any of these mibs currently? If not, we could remove the mibs to silence the spam on process restart.

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 5:06 pm
by benhank
Now in case all you fellow nagiosians, who may or may not be crackin up laughing at my terrible imitation of being a real IT guy, are wonderin "how does this guy keep his job?" All I can say is " cameras + tape recorders + upper management offices = "If I go down, we ALL goin' down"

But, aB did you know that in the snmptt.ini file if you change
DEBUGGING_FILE_HANDLER = /var/log/snmptt/snmptthandler.debug
to
DEBUGGING_FILE_HANDLER = /var/log/snmptt/snmptthandler.debug # enabled by BH 12/09/13,
you end up on the forums getting laffed at?
you can lock it up man

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 5:11 pm
by sreinhardt
you might want to change that to:

# DEBUGGING_FILE_HANDLER = /var/log/snmptt/snmptthandler.debug # disabled by BH 12/09/13

this really isnt needed and is going to take a ton of space as you do more and more with traps.

Re: weird snmptt issue

Posted: Mon Dec 09, 2013 5:12 pm
by abrist
Lock, stock, and two smoking IT guys.