Re: Possible bug in snmp 5.4.2.1 / snmptrapd double free()

2009-02-23 Thread Ralf S. Engelschall
On Fri, Feb 06, 2009, Christian Lete wrote:

 [...]
 I'm having problems to run snmptrapd, I keep getting the following error:
 [...]
 Warning: no access control information configured.
 This receiver will *NOT* accept any incoming notifications.
 *** glibc detected *** snmptrapd: free(): invalid pointer:
 0x00533308 ***
 [...]

Sould be now already fixed with the latest snmp package.

   Ralf S. Engelschall
   r...@engelschall.com
   www.engelschall.com

__
OpenPKG http://openpkg.org
Developer Communication List   openpkg-dev@openpkg.org


Re: Possible bug in snmp 5.4.2.1 / snmptrapd double free()

2009-02-23 Thread Christian Lete
Hi Ralph,

 Sould be now already fixed with the latest snmp package.

Yes, works fine now, thank you for the help.

Regards,

Christian Lete
__
OpenPKG http://openpkg.org
Developer Communication List   openpkg-dev@openpkg.org


Re: Possible bug in snmp 5.4.2.1 / snmptrapd double free()

2009-02-16 Thread Bernhard Reiter
On Freitag, 6. Februar 2009, Christian Lete wrote:
 This only happens on openpkg' binary , if I compile the source and run
 the binary works perfectly.

 Not sure what could be the reason for this. Suggestions are welcome :)

Slightly different system properties between the machine where you ran
the binary and the build machine.

Could probably only analysed with access to both machines and 
a comparison.

-- 
Managing Director - Owner: www.intevation.net  (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


signature.asc
Description: This is a digitally signed message part.


Re: Possible bug in snmp 5.4.2.1 / snmptrapd double free()

2009-02-16 Thread Bernhard Reiter
On Montag, 16. Februar 2009, Bernhard Reiter wrote:
 On Freitag, 6. Februar 2009, Christian Lete wrote:
  This only happens on openpkg' binary , if I compile the source and run
  the binary works perfectly.
 
  Not sure what could be the reason for this. Suggestions are welcome :)

Nevermind, I saw your question was already answered on the users list.
Sorry for the noise.

 Slightly different system properties between the machine where you ran
 the binary and the build machine.

 Could probably only analysed with access to both machines and
 a comparison.



-- 
Managing Director - Owner: www.intevation.net  (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


signature.asc
Description: This is a digitally signed message part.


Possible bug in snmp 5.4.2.1 / snmptrapd double free()

2009-02-06 Thread Christian Lete
Hi,

I have sent the report to the user list, but has not been published,
sorry if its a duplicate.

Heres the issue


I'm having problems to run snmptrapd, I keep getting the following error:

Warning: no access control information configured.
This receiver will *NOT* accept any incoming notifications.
*** glibc detected *** snmptrapd: free(): invalid pointer:
0x00533308 ***
=== Backtrace: =
/lib64/libc.so.6[0x2b11281a4684]
/lib64/libc.so.6(cfree+0x8c)[0x2b11281a7ccc]
snmptrapd[0x40c350]
snmptrapd[0x40d63f]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2b11281508b4]
snmptrapd(realloc+0x1b9)[0x40b8c9]
=== Memory map: 
0040-0058 r-xp  fd:02 18546700
 /opt/openpkg/sbin/snmptrapd
0078-00795000 rw-p 0018 fd:02 18546700
 /opt/openpkg/sbin/snmptrapd
00795000-007ce000 rw-p 00795000 00:00 0
10794000-10838000 rw-p 10794000 00:00 0  [heap]
2b1127afb000-2b1127b15000 r-xp  fd:02 8880609
 /lib64/ld-2.5.so
2b1127b15000-2b1127b16000 rw-p 2b1127b15000 00:00 0
2b1127b1c000-2b1127b1d000 rw-p 2b1127b1c000 00:00 0
2b1127d15000-2b1127d16000 r--p 0001a000 fd:02 8880609
 /lib64/ld-2.5.so
2b1127d16000-2b1127d17000 rw-p 0001b000 fd:02 8880609
 /lib64/ld-2.5.so
2b1127d17000-2b1127d19000 r-xp  fd:02 8880419
 /lib64/libdl-2.5.so
2b1127d19000-2b1127f19000 ---p 2000 fd:02 8880419
 /lib64/libdl-2.5.so
2b1127f19000-2b1127f1a000 r--p 2000 fd:02 8880419
 /lib64/libdl-2.5.so
2b1127f1a000-2b1127f1b000 rw-p 3000 fd:02 8880419
 /lib64/libdl-2.5.so
2b1127f1b000-2b1127f3 r-xp  fd:02 8880461
 /lib64/libnsl-2.5.so
2b1127f3-2b112812f000 ---p 00015000 fd:02 8880461
 /lib64/libnsl-2.5.so
2b112812f000-2b112813 r--p 00014000 fd:02 8880461
 /lib64/libnsl-2.5.so
2b112813-2b1128131000 rw-p 00015000 fd:02 8880461
 /lib64/libnsl-2.5.so
2b1128131000-2b1128133000 rw-p 2b1128131000 00:00 0
2b1128133000-2b112827d000 r-xp  fd:02 8880481
 /lib64/libc-2.5.so
2b112827d000-2b112847c000 ---p 0014a000 fd:02 8880481
 /lib64/libc-2.5.so
2b112847c000-2b112848 r--p 00149000 fd:02 8880481
 /lib64/libc-2.5.so
2b112848-2b1128481000 rw-p 0014d000 fd:02 8880481
 /lib64/libc-2.5.so
2b1128481000-2b1128488000 rw-p 2b1128481000 00:00 0
2b1128488000-2b1128495000 r-xp  fd:02 8890384
 /lib64/libgcc_s-4.1.2-20080102.so.1
2b1128495000-2b1128695000 ---p d000 fd:02 8890384
 /lib64/libgcc_s-4.1.2-20080102.so.1
2b1128695000-2b1128696000 rw-p d000 fd:02 8890384
 /lib64/libgcc_s-4.1.2-20080102.so.1
2b112c00-2b112c021000 rw-p 2b112c00 00:00 0
2b112c021000-2b113000 ---p 2b112c021000 00:00 0
7fff82f99000-7fff82faf000 rw-p 7fff82f99000 00:00 0  [stack]
ff60-ffe0 ---p  00:00 0  [vdso]
Aborted

kernel version: 2 2.6.18-92.1.1.el5.028stab057.2 #1 SMP Mon Jul 21
17:08:31 MSD 2008 x86_64 x86_64 x86_64 GNU/Linux
net-snmp -version: 5.4.2.1
centos 5.2

Im running this in a VZ container



This only happens on openpkg' binary , if I compile the source and run
the binary works perfectly.

Not sure what could be the reason for this. Suggestions are welcome :)

Thanks!

Christian Lete
__
OpenPKG http://openpkg.org
Developer Communication List   openpkg-dev@openpkg.org