Re: [Fwd: 5.3.x segfaults with signal handling and log files?]

For the record:

We're 100% certain that these segfaults are related to re-parsing of the
configuration as it relates to specific IP address bindings that we do.

We do not see them on non-multihomed systems, only on systems where we
explicitly identify a bind address for the agent (dedicated mgmnt
interface)

~BAS


On Mon, 2008-04-14 at 14:06 -0400, Brian A. Seklecki wrote:
> On Sat, 2008-04-12 at 00:30 +0200, Thomas Anders wrote:
> > Brian A. Seklecki schrieb:
> > > This is a crash with full tracebcak on 5.3.2 on FreeBSD 6.2/amd64 in
> > > log_handler_file(). We see it at the top of the hour when newsyslog(8)
> > > rotates files and passes SIGHUP to various daemons.
>
> Man there are a lot of bug [reports]. I filed mine:
>
> http://sourceforge.net/tracker/index...94&atid=112694
>
> We think that it has something to do with re-parsing the "agentAddress"
> tokens in snmpd.conf(5), so we're running the agent with a wildcard
> bound address.
>
> We're also running a 5.4 binary (FreeBSD port was upgraded). Every time
> that we build the 5.4 binary with debugging, it segfaults. Will report
> that separately.
>
> ~BAS
>
> > > Issues #1473289 and
> > > #1681977 come to mind.
> >
> > Please submit to http://www.net-snmp.org/bugs so it won't get lost and
> > post a note to the list.
> >
> >
> > +Thomas
--
Brian A. Seklecki <bseklecki@collaborativefusion.com>
Collaborative Fusion, Inc.


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757...un.com/javaone
_______________________________________________
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/...net-snmp-users