Bug 991213

Summary: snmpd hangs starting when sendmail queue groups are defined
Product: Red Hat Enterprise Linux 6 Reporter: Kelsey Cummings <kgc>
Component: net-snmpAssignee: Jan Safranek <jsafrane>
Status: CLOSED ERRATA QA Contact: Dalibor Pospíšil <dapospis>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: dapospis
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: snmpd, the SNMP daemon, wrongly parsed Sendmail configuration files with enabled queue groups. Consequence: snmpd entered endless loop on startup. Fix: Parsing of the configuration file with queue groups was fixed. Result: snmpd does not enter endless loop.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 22:52:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch none

Description Kelsey Cummings 2013-08-01 21:07:10 UTC
Created attachment 781775 [details]
patch

Description of problem:

A bug in the config parsing leads to a endless loop when it encounters queue groups defined in the cf.  Fixed upstream in 5.6


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

5.5-44

How reproducible:

100%


Steps to Reproduce:
1. define sendmail queue group in sendmail.cf

eg:

cd /etc/mail;

add to sendmail.mc
define(`QUEUE_DIR', `/var/spool/mqueue/q*')dnl
QUEUE_GROUP(`mqueue', `F=f, I=1m, R=10')dnl 

make && make restart

2. attempt to start snmpd

Actual results:

It hangs.

Expected results:

It should start.


Additional info:

Patch is back ported from 5.6 and appears to fix the bug, allowing snmpd to start when sendmail queue groups are defined.

Comment 6 errata-xmlrpc 2013-11-21 22:52:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1693.html