Menu
▾
▴
#1399 ifTable reports netsnmp_assert index == tmp failed
In certain situations the Linux kernel will give the
same interface a different index number. The agent
curently tries to correlated index to interface name,
thus the above assertion.
To reproduce, pick an interface and figure out what
kernel module it uses. Then : ifdown ethX; rmmod modX;
modprobe modX; ifup ethX
You will note that the interface entry in /proc/net/dev
is moved to the last line (if it wasn't already) and
all stats are re-set.
will start a discussion on coders for the proper fix...
Logged In: YES
user_id=1180631
I have the same problem on loaded pppoe server.
Logged In: NO
I am wondering why so few users seem to stumble upon this
bug. Although it certainly could easier be fixed in the
kernel, you all know this won't happen. I am waiting for a
fix for almost half a year, so could you please clarify what
is going to happen with this bug? Thank you.
Logged In: YES
user_id=1180631
I`ve looked to sendmail code around interfaces discovery. It
is really very hard to detect interfaces :(
Logged In: YES
user_id=1371568
I've made a patch against the latest release that fixes this
for me. Patch number is #1513191.
Logged In: NO
It is only recently that I have also encountered that same
problem and snmp_assert is failing on me with error code
407. That is happening since I started up a vtund and am
currently establishing virtual tunnels. So each time a
tunnel is created it gets new IfName, i.e.:
snmpwalk -v 2c -c public localhost ifName
IF-MIB::ifName.1 = STRING: eth0
IF-MIB::ifName.2 = STRING: lo
IF-MIB::ifName.3 = STRING: eth1
IF-MIB::ifName.4 = STRING: tunl0
IF-MIB::ifName.6 = STRING: tun0
IF-MIB::ifName.7 = STRING: tun0
IF-MIB::ifName.8 = STRING: tun0
IF-MIB::ifName.9 = STRING: tun0
IF-MIB::ifName.10 = STRING: tun0
IF-MIB::ifName.11 = STRING: tun0
IF-MIB::ifName.12 = STRING: tun0
IF-MIB::ifName.13 = STRING: tun0
IF-MIB::ifName.14 = STRING: tun0
IF-MIB::ifName.15 = STRING: tun0
IF-MIB::ifName.16 = STRING: tun0
IF-MIB::ifName.17 = STRING: tun0
IF-MIB::ifName.18 = STRING: tun0
IF-MIB::ifName.20 = STRING: tun0
IF-MIB::ifName.21 = STRING: tun0
IF-MIB::ifName.23 = STRING: tun0
IF-MIB::ifName.24 = STRING: tun0
IF-MIB::ifName.25 = STRING: tun0
IF-MIB::ifName.26 = STRING: tun0
IF-MIB::ifName.27 = STRING: tun0
IF-MIB::ifName.29 = STRING: tun0
IF-MIB::ifName.35 = STRING: tun0
IF-MIB::ifName.37 = STRING: tun0
IF-MIB::ifName.38 = STRING: tun0
IF-MIB::ifName.39 = STRING: tun0
IF-MIB::ifName.40 = STRING: tun0
IF-MIB::ifName.41 = STRING: tun0
IF-MIB::ifName.42 = STRING: tun0
If the tunnel dies and is restarted, the new iface tun0 will
get ifName.43 which I presume causes those error messages in
syslog.
Can anyone shed a light on how this error lines can be fixed?
Regards,
-Nikolay Kichukov
It's also true for dynamic ppp interfaces ! This is BUG in snmp.
Use this PATCH: http://sourceforge.net/tracker/index.php?func=detail&aid=1513191&group_id=12694&atid=312694