[Samba] winbindd: Exceeding 200 client connections, no idle connection found

[Rene]

Jeremy Allison schrieb:
> On Mon, Jul 13, 2009 at 11:53:15AM -0400, Linux Addict wrote:
>> On Sun, Mar 22, 2009 at 3:37 PM, Elvar <elvar at elvar.org> wrote:
>>
>>>
>>> Elder Souza wrote:
>>>
>>>> No prob Jeremy, thanx for your help!
>>>>
>>>> Elder Souza
>>>> (71) 9972-7573 / (71) 8801-5734
>>>>
>>>>
>>>> On Tue, Oct 21, 2008 at 5:47 PM, Jeremy Allison <jra at samba.org> wrote:
>>>>
>>>>
>>>>
>>>>> On Tue, Oct 21, 2008 at 05:44:05PM -0300, Elder Souza wrote:
>>>>>
>>>>>
>>>>>> It has been fixed after what version? Do you know?
>>>>>>
>>>>>>
>>>>> Don't have the time to check the release
>>>>> notes right now, but it's definately fixed
>>>>> in 3.0.32 and 3.2.4.
>>>>>
>>>>> Jeremy.
>>>>>
>>>>>
>>>>>
>>> I just downloaded version 3.0.33 and when I view the local.h file I still
>>> see 200 defined as the max simultaneous connections. Is it really fixed?
>>> Some of my installations require more than 200 simultaneous connections. I'm
>>> still using an older version but until I modified this to 400+ I had
>>> problems.
>>>
>>> /* Max number of simultaneous winbindd socket connections. */
>>> #define WINBINDD_MAX_SIMULTANEOUS_CLIENTS 200
>>>
>>>
>>>
>>>
>>>
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>>
>>
>> I am using  3.2.4 but I still get this messages. I had many production
>> servers hit 100% CPU due to winbind. I had to stop winbind 3 times through
>> rc script to stop winbind.
>>
>> I didn't have verbose log enabled, but I would go straight and upgrade if
>> you guys think this is resolved in latest versions.
> 
> Ah. My statement that this was fixed in 3.2.4 was wrong, sorry
> about that.
> 
> I've checked back in the release notes and the fix for this
> bug (3204) was discovered by Richard Sharpe in Jan 2009,
> and 3.2.4 dates from 18 September 2008.
> 
> The fix went into the 3.2 tree on 2009-01-08, and so
> it will have been fixed on the 03 February 2009 release
> Samba 3.2.8 and above. Sorry for the mistake in claiming
> it was fixed in 3.2.4.
> 
> Jeremy.


Hi there,

got the same problem on a Samba 3.3.1 installation.

winbindd log is filling up faster than logrotate is able to clean it, 
and my machine finally ends up with a full partition.

Searched the Web now half the day and found that it should be solved in 
3.2.8. Is there any other known Issue how this behavior can occur?


René