winbind(d) exhibits large memory leak

frilled

For quite some time I was wondering why my workstation (512 MB) starts swapping memory to disk so soon after starting up. Now I found the culprit: winbindd randomly starts using ~70% of memory.

Unfortunately, this applies to all production servers, too, though the problem is somewhat less severe since most of them got more memory. Nevertheless, it slows down the machines and hogs system ressources.

I absolutely need winbind to integrate with out Windoze domain, so dropping it is not an option.

Anyone else seen this? I'm using "stable" (obviously not) samba-3.0.10, but I am not completely sure it started with 3.0.10 or 3.0.9.

Anyone else knows about this? Is there a patch around or is the issue addressed in 3.0.11?
_________________
"Failure is not an option!"
"Sir, we are out of further options."

j-m · Retired Dev Joined: 31 Oct 2004 Posts: 975

What version is your kernel?

frilled · Posted: Tue Mar 01, 2005 3:39 pm Post subject:

plut0 · Apprentice Joined: 21 Dec 2004 Posts: 272

I am having this problem also. Server has 512mb of ram and everyday winbindd eats most of it up. This in case causes the machine to either start killing processes, have very slow respones or a total lockup.

I am using 2.6.11-hardened-r15 kernel. This happens almost everyday now since I implemented it.

frilled · Posted: Thu Sep 22, 2005 4:04 pm Post subject:

The problem has not ceased at all. I'm up to kernel 2.6.12-r10 and Samba 3.0.14a (on the production servers) and 3.0.20 on my workstation and a test server. Supposedly winbindd has been rewritten for 3.0.20, so we'll have to see whether they got that wreckage turned into something usable :/
_________________
"Failure is not an option!"
"Sir, we are out of further options."