Bug 251319 - Possible memory leak in saslauthd
Summary: Possible memory leak in saslauthd
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cyrus-sasl
Version: 6
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Steve Conklin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-08 11:25 UTC by Radek Hladik
Modified: 2008-01-04 17:17 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-01-04 17:17:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Radek Hladik 2007-08-08 11:25:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6

Description of problem:
After few days saslauthd processes allocates all memory (4GB) and casues server to swap. Restarting saslauthd solves the problem for another few days. I can see on memory monitoring that this is continuous so I assume there is some small memory leak but I do not know how to debug what is saslauthd doing. Daemon is functioning properly and log shows nothing interesting.
I am using saslauthd to authenticated to mysl via pam.
The only thing sasluthd logs is 
Aug  8 10:10:30 rdesign saslauthd[19126]: do_auth         : auth failure: [user=username.example.com] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error]
But I suggest that this is normal error due to password mistake. And there is max 20 of these messages per day.
Even shutting down the service looks normaly:
Aug  8 12:59:17 rdesign saslauthd[19122]: server_exit     : master exited: 19122
Aug  8 12:59:17 rdesign saslauthd[23345]: detach_tty      : master pid is: 23345

Unfortunately I could not try to reproduce it on other server as I do not have similar server.


Version-Release number of selected component (if applicable):
cyrus-sasl-2.1.22-4

How reproducible:
Didn't try


Steps to Reproduce:
1.
2.
3.

Actual Results:


Expected Results:


Additional info:

Comment 1 Steve Conklin 2008-01-04 17:17:54 UTC
This bug was opened against Fedora 6, which has reached end of life. If this can
be reproduced with a later release, please open another bug.


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