Thanks Magnus. Your suggestion seems to have worked. I removed the -c from
the command line and I get only one dynamic port.
But the same options were being used in an older version. I wasn't getting
duplicate traps with the same options used.
Has the behaviour changed with NET-SNMP version 5.4.2.1. Shouldn't it read
the config file once if it knows the user is provides it from the default
location?
Regards,
Akshata
On Sat, Mar 26, 2011 at 11:20 AM, Magnus Fromreide <[email protected]>wrote:
> On Sat, 2011-03-26 at 10:58 -0700, akshata s harkantra wrote:
> > Hi Dave,
> >
> > Thanks for your response. I am startring snmpd with the following
> > options
> >
> > /usr/sbin/snmpd -c /etc/snmp/snmpd.conf -p /tmpfs/snmpd.pid -f -Le
> > -Dread_config
> >
> > Also, I have only a single entry of trap2sink line in the conf file.
> >
> > I am sure that even if I start snmpd only once I get two entries in
> > snmpd.log
> >
> > Turning on AgentX master support.
> > Turning on AgentX master support.
> >
> > Is this an issue? Also the read_config debug token shows me its
> > repeating the read. Have attached the log. But this results in
> > duplicate traps. How can this be avoided?
>
> I'd guess your default configuration file is /etc/snmp/snmpd.conf so it
> reads it twice since it did it once as the default configuration file
> and once as the user supplied configuration file.
>
> If this is the case then you could fix it by removal of
> '-c /etc/snmp/snmpd.conf' from the command line
>
> Could you please give that a try.
>
> /MF
>
> > Looking forward for your response.
> >
> > Regards,
> > Akshata
> >
> >
> >
> >
> > On Sat, Mar 26, 2011 at 3:43 AM, Dave Shield
> > <[email protected]> wrote:
> > On 26 March 2011 06:00, akshata s harkantra
> > <[email protected]> wrote:
> > > I am facing a strange behaviour with snmp running on my
> > linux box. I see
> > > that two dynamic ports are opened by the daemon
> >
> >
> > > I have only single trap2sink entry in my configuration file
> > snmpd.conf.
> >
> >
> > > Not sure why I am seeing two ports. Due to this I also get
> > duplicate traps
> > > at the receiver whenever a trap event occurs. Please advise
> > on why such a
> > > behavior is seen.
> >
> >
> >
> > The most likely explanation is that the snmpd.conf file is
> > being read twice,
> > and hence two trap destinations are being set up.
> >
> > You haven't said anything about how you are starting the agent
> > - i.e. what
> > command this uses - or the location(s) of your snmpd.conf
> > file(s).
> >
> > Try shutting down the agent, and then restarting it manually,
> > using the
> > command-line options
> >
> > -f -Le -Dread_config
> >
> > plus any other options that you normally use.
> > This will show the processing of config file entries, and
> > hopefully
> > indicate whether this is indeed the cause.
> >
> > Dave
> >
> >
> ------------------------------------------------------------------------------
> > Enable your software for Intel(R) Active Management Technology to meet
> the
> > growing manageability and security demands of your customers. Businesses
> > are taking advantage of Intel(R) vPro (TM) technology - will your
> software
> > be a part of the solution? Download the Intel(R) Manageability Checker
> > today! http://p.sf.net/sfu/intel-dev2devmar
> > _______________________________________________ Net-snmp-coders mailing
> list [email protected]
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
>
>
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
