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

[Linux Addict]

On Mon, Jul 13, 2009 at 11:53 AM, Linux Addict <linuxaddict7 at gmail.com>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.
>
>
>
>   winbindd: Exceeding 200 client connections, no idle connection found
> [2009/07/09 16:50:36,  0] winbindd/winbindd.c:process_loop(955)
>   winbindd: Exceeding 200 client connections, no idle connection found
> [2009/07/09 16:50:36,  0] winbindd/winbindd.c:process_loop(974)
>   winbindd: Exceeding 200 client connections, no idle connection found
> [2009/07/09 16:50:36,  0] winbindd/winbindd.c:process_loop(955)
>   winbindd: Exceeding 200 client connections, no idle connection found
> [2009/07/09 16:50:36,  0] winbindd/winbindd.c:process_loop(974)
>   winbindd: Exceeding 200 client connections, no idle connection found
> [2009/07/09 16:51:41,  1] lib/util_tdb.c:tdb_validate_and_backup(1424)
>   tdb '/var/lib/samba/winbindd_cache.tdb' is valid
> [2009/07/09 16:51:41,  1] lib/util_tdb.c:tdb_validate_and_backup(1434)
>   Created backup '/var/lib/samba/winbindd_cache.tdb.bak' of tdb
> '/var/lib/samba/winbindd_cache.tdb'
> [2009/07/09 16:51:41,  0]
> winbindd/winbindd_cache.c:initialize_winbindd_cache(2374)
>   initialize_winbindd_cache: clearing cache and re-creating with version
> number 1
> [2009/07/09 16:51:42,  1] lib/util_tdb.c:tdb_validate_and_backup(1424)
>   tdb '/var/lib/samba/winbindd_cache.tdb' is valid
> [2009/07/09 16:51:42,  1] lib/util_tdb.c:tdb_validate_and_backup(1434)
>   Created backup '/var/lib/samba/winbindd_cache.tdb.bak' of tdb
> '/var/lib/samba/winbindd_cache.tdb'
> user at hostname$ rpm -qa |grep sam
> samba-client-3.2.4-1
> samba-3.2.4-1
> samba-debuginfo-3.2.4-1
> samba-swat-3.2.4-1
> samba-common-3.2.4-1
> samba-doc-3.2.4-1
>
>
>
>
>
>
Looks like this where the bug was tracked.

https://bugzilla.samba.org/show_bug.cgi?id=3204