winbindd from the samba-3.0.10 stable x86 ebuild exhibits a huge memory leak. I run Samba 3.0.10 with winbind in ADS mode to authenticate against our Micro$oft domain. After running for couple of hours, winbindd quickly eats up memory, swapping other processes to disk and slowing down the machines. This behaviours happens on my workstation and 7 production servers. I had to add a nightly restart during the night to avoid bogging down the machines. Built with USE="mmx sse nptl X freetype bindist doc qt qtmt kde openal arts gtk2 gtk gnome alsa samba winbind kerberos ldap mysql gd apache2 aalib dga tiff snmp unicode xinerama -acl gnokii oscar xvid". Kernel on all machines is gentoo-dev-sources-2.6.10-r6. Servers have various memory sizes from 512k MB to 2G. Reproducible: Always Steps to Reproduce: 1. Emerge samba with USE-flags mentioned above 2. Put it in ADS mode and start winbindd 3. Use the machine and watch winbindd grow Actual Results: winbindd uses like 70% of memory overnight Expected Results: Sane behaviour
Please try the 3.0.11 (currently marked unstable), it might contain the fix you need: Common bugs fixed in 3.0.11 include: o Crash in smbd when using CUPS printing. o Parsing error of other SIDs included in the user_info_3 structure returned from domain controllers. o Inefficiencies when searching non-AD LDAP directories. o Failure to expand variables in user domain attributes in tdbsam and ldapsam. o Memory leaks. o Failure to retrieve certain attribute when migrating from a Windows DC to a Samba DC via 'net rpc vampire'. o Numerous printing bugs bugs including memory bloating on large/busy print servers. o Compatibility issues with Exchange 5.5 SP4. o sendfile fixes. Additional features introduced in Samba 3.0.11: o Winbindd performance improvements. o More 'net rpc vampire' functionality. o Support for the Windows privilege model to assign rights to specific SIDs. o New administrative options to the 'net rpc' command.
I will try to upgrade in a test environment and get back to you on Monday/Tuesday.
Looks promising so far on my workstation where the problem used to show up after less than an hour. Any known caveats with the 3.0.11 ebuild I should be aware of?
no, its a bugfix only release. It's only in ~x86 for testing and i think we can bump it to stable soon. (esp. when there are quite serious issues with winbind in 3.0.10 as it seems)
I would definitely consider that a good idea. Give me the weekend to see if the new version fixes the trouble. 3.0.10 in this configuration should be considered dangerous for production servers.
Coming back after the weekend reveals that the bug was not completely fixed in 3.0.11, although it is not as bad as before. When I came in today, winbindd's memory usage was about 29%. When I left Friday afternoon I had just booted the machine, making winbindd use ~0,4% of memory. Still no go for production environment :-/
Hmm, thats bad. Changelog for 3.0.12-rc1 lists memory leaks again :( I hope the new samba4 will have some more strict checking :( Anyway, can you please bug upstream for this issue : https://bugzilla.samba.org/ (and send me a note, or file a bug if there's some news on that topic) Many thanks for the testing !
3.0.13?
3.0.13 looks way better by now, but I refuse to declare it "working" as of now :) Gotta see for a little longer.
This one is obsolete for me now as I was forced to go to 3.0.14a anyway to keep it working with a pure 2003 domain. Follow-up is #98303. Thank you.
fixed due to 3.0.14a-r2 about to go stable
