On 30 June 2011 08:01, <[email protected]> wrote:
> I need to enable net-snmp Debug logs.
>
> Can somebody explain me how to confiqure it to get debug logs.
$ man snmpd
-D[TOKEN[,...]]
Turn on debugging output for the given TOKEN(s). Without any
tokens specified, it defaults to printing all the tokens (which
is equivalent to the keyword "ALL"). You might want to try ALL
for extremely verbose output. Note: You can not put a space
between the -D flag and the listed TOKENs.
$ man snmp.conf
doDebugging (1|0)
turns on debugging for all applications run if set to 1.
debugTokens TOKEN[,TOKEN...]
defines the debugging tokens that should be turned on when doDe‐
bugging is set. This is equivalent to the -D option.
Note that if you want to turn on debugging via the config file, but *only*
for the agent (rather than all SNMP commands), then you'd need a block
something like
[snmp]
doDebugging 1
debugTokens this,that,theother
in your snmpd.conf file.
> Where do I see the logs?
Debug output goes to the same place as any other logging output from
the agent - typically via syslog to /var/log/messages or a similar default
log file.
If you run the agent using the options ' -f -Le' then you'll see the output
on the command line. That tends to be how I work when I'm debugging
a problem.
Dave
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
