snmpd sigsegv

[Anatoly Pugachev]

System:

Ubuntu 9.04 x86_64 , 2.6.28-16-server kernel
snmpd-5.4.1~dfsg-12ubuntu3.1 package.

How to reproduce:

put to /etc/snmp/snmpd.conf an "exec" directive, even simple "exec echo hello" will do.

try to query snmpd for above results, I've used command line:

$ snmpwalk -v 1 -c ro localhost .extOutput.1

getting in /var/log/messages:

Nov 27 17:41:15 muse01 kernel: [11062.076227] snmpd[25032]: segfault at 60 ip 00007f29e357748c sp 00007fff37639800 error 4 in libnetsnmpmibs.so.15.1.0[7f29e]

running snmpd in a gdb to get backtrace and logs is in attachment.

[Anatoly Pugachev (matorola)]

sorry for wrong initial Bazaar assign, can someone remove it? thanks

[Chuck Short (zulcss)]

Can you attach your /etc/snmp/snmp.conf?

Thanks
chuck

[Anatoly Pugachev (matorola)]

/etc/snmp/snmpd.conf :

rocommunity public
disk /

exec echo /bin/echo "hi there"

com2sec paranoid default public
com2sec readonly default public

group MyROSystem v1 paranoid
group MyROSystem v2c paranoid
group MyROSystem usm paranoid
group MyROGroup v1 readonly
group MyROGroup v2c readonly
group MyROGroup usm readonly
group MyRWGroup v1 readwrite
group MyRWGroup v2c readwrite
group MyRWGroup usm readwrite

view all included .1 80
view system included .iso.org.dod.internet.mgmt.mib-2.system

access MyROSystem "" any noauth exact system none none
access MyROGroup "" any noauth exact all none none
access MyRWGroup "" any noauth exact all all none

on snmpd startup, there's a message in syslog:

$ tail /var/log/syslog
Nov 30 19:15:22 muse01 snmpd[26108]: duplicate table data attempted to be entered. row exists

[Anatoly Pugachev (matorola)]

There's a difference in community name in my last post and first post, I've intentionally changed community name, not to show it to the public, but bug still arise even with different (i.e. "public") RO community name. Thanks.

[Chuck Short (zulcss)]

This has been fixed in lucid.

Regards
chuck

[Anatoly Pugachev (matorola)]

I don't see a fix is released... You're telling that it was fixed in lucid, which is not what I've reported on.
Any chance it will be back-ported to jaunty or i should upgrade all my servers to the last ubuntu release every time a bug has been fixed?