Bug 190422

Summary: Memory leak on Winbind
Product: Red Hat Enterprise Linux 3 Reporter: Stuart Ellis <stuart>
Component: sambaAssignee: Simo Sorce <ssorce>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jplans, samba-bugs-list
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 18:44:53 UTC Type: ---
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
Samba configuration
none
Kerberos configuration file none

Description Stuart Ellis 2006-05-02 07:43:34 UTC 
Description of problem:

Winbind process periodically begins to leak memory, and memory utilisation then
grows without limit until the service is restarted.

Winbind has been set to run in double daemon mode with option in
/etc/sysconfig/samba.

The servers are authenticating against a Windows 2000 domain controller of
approx 6,000 accounts.

No nscd process is running.


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

Systems use samba-3.0.9-1.3E.7 package as supplied by RHN.

How reproducible:

Run the servers for a long time :)

Actual results:

Memory utilisation begins to grows from 4% and continues to rise until service
is restarted.

Expected results:

Memory utilisation should be stable.


Additional info:

Attaching smb.conf and krb5.conf.
Comment 1 Stuart Ellis 2006-05-02 07:43:35 UTC 
Created attachment 128471 [details]
Samba configuration
Comment 2 Stuart Ellis 2006-05-02 07:44:48 UTC 
Created attachment 128472 [details]
Kerberos configuration file

Uploaded krb5.conf.
Comment 3 RHEL Program Management 2007-10-19 18:44:53 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.