notify queue seg fault bug

[Kevin J. Schmidt]

I pulled down the beta code, but this did not fix the seg fault bug. The
box has one interface, and it's a standard Ethernet interface (eth0).
The machine is Linux Red Hat 7.2 running kernel 2.4.16.

Do you have any other suggestions? Our trap daemon is in production, and
I need to find a fix for it quick. 

Thanks!
-Kevin

On Wed, 2002-06-12 at 17:11, Jochen Katz wrote:
> Hi,
> 
> > Ok, it looks like SNMP++3.2 beta 3 fixes a seg fault bug in the notify
> > queue code. This will probably fix my problem.
> 
>  > CNotifyEvent::Callback (this=0x81befa0, target=@0x0,
>  > pdu=@0xbffff394, status=-22)
>  >    at notifyqueue.cpp:295
> 
> the 3.2beta version of snmp++ contains the fix for the problem. You 
> could add the changes from notifyqueue.cpp to the version you're using.
> 
> 
>  > What caught my eye was is the stats=-22 at #1. According to
>  > snmperrs.h, -22 is SNMP_CLASS_TL_FAILED. My first question is
>  > whether or not this is the same error that the
>  > CNotifyEvent::Callback method is seeing, and if so what is causing
>  > it? Also, does anyone know if this is what could cause the SEG
>  > faults I'm seeing?
> 
> The -22 comes from  receive_snmp_notification() and indicates a socket 
> problem. Are you listening on multiple interfaces and one is shut down 
> (a ppp link for example)?
> 
> 
> > I know that 3.2 is beta,
> > but does anyone who's working on 3.2 see any problems with using 3.2
> > strictly for SNMPv1/2/3 trap and notifications?
> 
> No problems from my side. Frank will test the beta version during the 
> weekend and if these tests are successful, the 3.2 will be released.
> 
> As I didn't receive any comments about the beta, either nobody (beside 
> me) is using it until now, or nobody had problems with it...
> 
> Kind regards,
>    Jochen
>