Bug 991213 - snmpd hangs starting when sendmail queue groups are defined
snmpd hangs starting when sendmail queue groups are defined
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: net-snmp (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Jan Safranek
Dalibor Pospíšil
Depends On:
  Show dependency treegraph
Reported: 2013-08-01 17:07 EDT by Kelsey Cummings
Modified: 2013-11-21 17:52 EST (History)
1 user (show)

See Also:
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:
Last Closed: 2013-11-21 17:52:05 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch (1.52 KB, patch)
2013-08-01 17:07 EDT, Kelsey Cummings
no flags Details | Diff

  None (edit)
Description Kelsey Cummings 2013-08-01 17:07:10 EDT
Created attachment 781775 [details]

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):


How reproducible:


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


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 17:52:05 EST
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.


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