Bug 161492 - Starting snmpd gives segmentation fault if lm_sensors is running
Summary: Starting snmpd gives segmentation fault if lm_sensors is running
Status: CLOSED DUPLICATE of bug 150199
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: net-snmp
Version: 4.0
Hardware: athlon
OS: Linux
Target Milestone: ---
: ---
Assignee: Radek Vokál
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-23 18:06 UTC by Peter Ison
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-24 08:11:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Peter Ison 2005-06-23 18:06:47 UTC
Description of problem:
This is a problem which appeared in RHEL4 after un upgrade from RHEL3.

"service snmpd restart" always reports failed on stopping the service and ok on 
starting. There are no other errors reported. After that "ps -A | egrep snmp" 
shows that snmpd is no longer running. 

With lm_sensors started "snmpd -f -Le" reports "segmentation fault". Stopping 
lm_sensors allows snmpd to run without the segmentation fault. I need them both 
running so that I can produce mrtg reports.

Running strace on the segmentation fault shows an access to /usr/lib/rpm/i386-
linux/macros. Perhaps this should be /usr/lib/rpm/athlon-linux/macros as is the 
case on another athlon pc running FC4 with lm_sensors and net-snmp-5.2.1-12 
with no problem.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.lm_sensors and net-snmp are started at boot
2."service snmpd restart" repeatedly shows failed on stopping; ok on starting 
3."ps -A | egrep snmp" shows that snmpd is not running
Actual results:
snmpd fails to start

Expected results:
snmpd should be running

Additional info:


sensor information is at /sys/devices/platform/i2c-1/1-0290

lm_sensors starts as S26 before snmpd at S50.

If I start snmpd and only then start lm_sensors, snmpd seems to keep running.  
That is an observation, not a solution to the problem.

Comment 1 Radek Vokál 2005-06-24 08:11:59 UTC
The bug is already fixed, will appear in next update

*** This bug has been marked as a duplicate of 150199 ***

Note You need to log in before you can comment on or make changes to this bug.