Description of problem: when starting snmpd it is crashing with segfault. Version-Release number of selected component (if applicable): net-snmp-5.4.2.1-1.fc10.x86_64 net-snmp-libs-5.4.2.1-1.fc10.x86_64 How reproducible: start snmpd. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: In attachement - strace /usr/sbin/snmpd -f > strace.log 2>&1
This happens to me too. I spent some time debugging, and I'm pretty convinced it is an upstreams bug in the inclusion of RPM header files: https://sourceforge.net/tracker/index.php?func=detail&aid=2357163&group_id=12694&atid=112694 Assuming you hit the same problem as I do, a workaround is to add "-I -hr_swinst" to the options in /etc/sysconfig/snmpd
I can confirm the issue. I tried to catch it here: https://admin.fedoraproject.org/updates/F10/FEDORA-2008-10451 but it got puched just after I entered that comment.
It's fallout of new rpm-4.6. I didn't notice getRpmPath() moved to rpmfileutil.h. The compiler does not find it -> it assumes 'int' is returned -> something very bad happens on x86_64. Panu, could you add #include<rpmfileutil.h> to rpmmacros.h?
Comitted to upstream. Will be backported soon in F10 and rawhide.
*** Bug 474144 has been marked as a duplicate of this bug. ***
rpm-4.6.0-0.rc1.8 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/rpm-4.6.0-0.rc1.8
Would it be possible to have net-snmp rebuilt against rpm-4.6.0-0.rc1.8 and pushed out? https://admin.fedoraproject.org/updates/rpm-4.6.0-0.rc1.8
The fixed rpm got to the koji buildroot this night, I'm compiling net-snmp right now. There are processes around and it takes some time to release fixed rpms.
net-snmp-5.4.2.1-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/net-snmp-5.4.2.1-2.fc10
net-snmp-5.4.2.1-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
rpm-4.6.0-0.rc1.8 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.