Red Hat Bugzilla – Bug 162130
winbindd, memory leak
Last modified: 2007-11-30 17:07:18 EST
Description of problem:
If samba is configured as "security = ADS" then winbindd begins to eat a memory
and then causes OOM-Killer to kill the process winbind, maybe then squid... and
Version-Release number of selected component (if applicable):
Samba-3.0.10-1.4E, Samba-client-3.0.10-1.4E, Samba-common-3.0.10-1.4E,
Steps to Reproduce:
1.Configure samba as ADS against Win2K Domain (see smb.conf).
2.Configure krb5 to get tickets on the Win2K Domain.
3.Make shares or do squid authentificate domain users using ntlm.
4.If server has RAM 512Mb - wait for one day OOM-killer to work.
Everything works ok while there is a free memory. When winbindd process fills
all the memory (memory leak is proved by valgrind, OOM-Killer starts to
stop(kill) almost all mandatory processes even sshd can be killed.
no memory leak, stable work of samba with krb5
winbindd works ok if it is configured with security = RPC.
There are lots records in log file
ads_cleanup_expired_creds: krb5_cc_remove_cred failed, err Ccache function
not supported: not implemented"
Created attachment 116161 [details]
File contains krb5.conf, smb.conf and log records
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Hello! currently no problem appeared... 4.5
Problem still exists:
current version of samba 3.0.10-1.4E.9
Since we had coverity and other checkers running against samba we fixed tons of
leaks and other errors.
Upstream we have no reports of leaks in winbindd and that's a component used a
lot these days.
I am confident it is ok.
I will test it again once wrt this problem soon to be sure.
I launched again on RHEL4 with
and smb configured as ADS
on 2.6.9-42.ELsmp #1 SMP
Results will or not be tomorrow :-)
After half of a month no mem leaks detected. It works!
Although this bugzilla was approved for RHEL 4.5, we were unable
to resolve it in time to be included in the release. Therefore
it is now proposed for RHEL 4.6.
Verified with 3.0.25b, there were in fact two major memleaks fixed (one with not
freeing an entire search result for users/groups from AD and the leakage of
expired krb5 creds, the later fixed with
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.