Bug 161317 - saslauthd memory leak
saslauthd memory leak
Product: Fedora Legacy
Classification: Retired
Component: cyrus-sasl (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Fedora Legacy Bugs
Depends On:
  Show dependency treegraph
Reported: 2005-06-22 07:50 EDT by Thomas Antony
Modified: 2007-04-18 13:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-27 17:11:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Thomas Antony 2005-06-22 07:50:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0

Description of problem:
I am running a mail server with postfix, cyrus-imapd, cyrus-sasl and mysql as backend.
Saslauthd uses with the time more and more memory until there is no swap space available and i run into huge troubles. Random daemons like ssh will exit because of not sufficient memory. I have to restart saslauthd on a regular basis to avoid this problem. 

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

How reproducible:
Didn't try

Steps to Reproduce:
1. -

Actual Results:  saslauthd use all available memory

Additional info:

I have set "pwcheck_method: saslauthd" in smtpd.conf

There a several posting on the cyrus mailing lists which concerns this bug. I don't know if it has been already been fixed.
Comment 1 Thomas Antony 2005-06-22 08:02:55 EDT
I did a mistake with the release number which is cyrus-sasl-2.1.18-2.2 and not
Comment 2 Thomas Antony 2005-06-29 09:19:12 EDT
Adding FLAGS="-c -n 0" to /etc/sysconfig/saslauthd avoids the problem for me,
but the memory leak is still there.
Comment 3 Juvenal A. Silva Jr. 2005-07-20 18:33:23 EDT
I found the same problem with Red Hat Enterprise Linux ES 3 with package
I'd like to really solve this problem, not only work-around it. Now I'm testing
the work-around to see if it's really effective.
I'm waiting your answer ASAP


Juvenal A. Silva Jr.
Comment 4 Eric Brunson 2005-08-03 17:37:07 EDT
Postings to the Cyrus mailing list indicate that this is a memory leak in the
PAM modules that most of us are using via saslauthd.  Would anyone care to
comment on that?
Comment 5 Thomas Antony 2005-11-27 17:11:22 EST
pam_mysql is causing the memory leaks.

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