[Pkg-samba-maint] DO NOT REPLY [Bug 3204] winbindd: Exceeding 200 client connections, no idle connection found

[samba-bugs at samba.org]

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





------- Comment #58 from vl at samba.org  2007-12-17 09:23 CST -------
You need to find out which of the winbind child processes hang and where. For
this you need to "strace -p" all the winbind processes while winbind is stuck.
You will very likely see that winbind sits in a select() system call. If it is
something else like for example fcntl64(), it would be very suspicious and
worth further investigation. If it is the case that it sits in fcntl, you will
see the file descriptor as the first argument of that syscall, from there you
can see which of the tdb files this via a "ls -l /proc/<winbind-pid>/fd". If it
is a select system call, is is very likely not the faulty process. What could
be is that it sits in a read() syscall. From there some detective work is
necessary to see which kind of file descriptor this is. It might be interesting
at this point to attach to the suspect process with gdb and do a backtrace with
"bt". This output might be very valuable. If you find out that your winbind
waits for a domain controller in a select or read system call, you might want
to do a subsequent tcpdump filtering out just this domain controller to find
out what sequence of requests winbind is doing and which ones lead to the
lock-up. It might also be something I just overlooked: It might very well be
possible that one of your tdb files is corrupt and winbind enters a 100% cpu
loop, thus not being able to reply at all anymore.

Volker


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.