From: SourceForge.net <no...@so...> - 2007-09-25 20:30:58
|
Bugs item #1794532, was opened at 2007-09-14 04:37 Message generated for change (Comment added) made by rstory You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1794532&group_id=12694 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: agent Group: None Status: Open Resolution: None Priority: 6 Private: No Submitted By: Matthias Saou (thias) >Assigned to: Robert Story (rstory) Summary: 5.4.1 segfault in ipAddressTable_container_load Initial Comment: Hi, I've just updated RHEL4 and RHEL5 servers to net-snmp 5.4.1, and have the exact same problem as described here on a few of them : http://sourceforge.net/mailarchive/forum.php?thread_name=46C1A8D9.7040607%40softax.pl&forum_name=net-snmp-coders I was previously running 5.4 fine, but it was spitting many useless messages to syslog, which 5.4.1 fixes on the servers where I tested it. What the problematic servers have in common are "duplicate addresses" : They either have VPN connections established (which are P-t-P with the same address on the local side), or are Xen hosts with many vif and veth interfaces. The other thing that strikes me is that no 64bit servers seem affected, only some 32bit ones. The segfault happens almost immediately after boot. All I get in /var/log/messages is : Sep 14 10:24:20 polar snmpd[31612]: netsnmp_assert !"registration != duplicate" failed agent_registry.c:535 netsnmp_subtree_load() Sep 14 10:24:20 polar last message repeated 2 times Sep 14 10:24:20 polar snmpd[31612]: Duplicate IP address detected, some interfaces may not be visible in IP-MIB Sep 14 10:24:20 polar snmpd[31612]: Duplicate IP address detected, some interfaces may not be visible in IP-MIB Backtrace : (gdb) bt #0 ipAddressTable_container_load (container=0x9907708) at ip-mib/ipAddressTable/ipAddressTable_data_access.c:347 #1 0x0016779d in ipAddressTable_container_init (container_ptr_ptr=0x24c5e0, cache=0x9906ec8) at ip-mib/ipAddressTable/ipAddressTable_data_access.c:137 #2 0x00162e9e in _ipAddressTable_initialize_interface (reg_ptr=0x0, flags=0) at ip-mib/ipAddressTable/ipAddressTable_interface.c:2003 #3 0x0014aceb in initialize_table_ipAddressTable () at ip-mib/ipAddressTable/ipAddressTable.c:104 #4 0x0014ad7a in init_ipAddressTable () at ip-mib/ipAddressTable/ipAddressTable.c:56 #5 0x001fd09a in init_mib_modules () at ../agent/mibgroup/mib_module_inits.h:20 #6 0x004290ef in main (argc=8, argv=0xbf969454) at snmpd.c:901 Please let me know if more information could be useful. ---------------------------------------------------------------------- >Comment By: Robert Story (rstory) Date: 2007-09-25 16:23 Message: Logged In: YES user_id=76148 Originator: NO can you try the attached patch? File Added: diff.ipaddress-patch ---------------------------------------------------------------------- Comment By: Matthias Saou (thias) Date: 2007-09-18 09:19 Message: Logged In: YES user_id=34811 Originator: YES Possibly. Of the 4 servers on which it happens for me, 3 are Xen hosts, thus have some bridge interfaces automatically configured, and the other one is an office gateway with a VPN setup requiring a bridge between a physical eth and a virtual tap interfaces. But in my case, these are all RHEL5 i386 (32bit), I haven't seen the problem on any RHEL4 i386 nor RHEL5 x86_64. And net-snmp doesn't even start, the segfault happens very early when starting it. And as I already wrote, 5.4 was running fine on those same servers. ---------------------------------------------------------------------- Comment By: Thomas Anders (tanders) Date: 2007-09-17 15:30 Message: Logged In: YES user_id=848638 Originator: NO Probably related to / a dup of 1792716. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1794532&group_id=12694 |