OS: RHE 3, kernal 2.4.21-32.0.1EL Samba version: samba-3.0.20 Removed RHE version of samba and compiled/installed samba-3.0.20. After running about 30-60 minutes, I get the following syslog msg: "winbindd: Exceeding 200 client connections, no idle connection found" Eventually this grinds the whole system to a halt, and remote & console logins become impossible while samba is running. I don't believe this is a case of too many users trying to connect, as only 2 workstations have been using the samba connectivity, so upping the connection limit in local.h doesn't sound like it would really fix the problem (a solution discovered via google). Appreciate any help here - more info (like the smb.conf) availabe if needed. _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
OS: RHE 3, kernal 2.4.21-32.0.1EL Samba version: samba-3.0.20 Removed RHE version of samba and compiled/installed samba-3.0.20. After running about 30-60 minutes, I get the following syslog msg: "winbindd: Exceeding 200 client connections, no idle connection found" Eventually this grinds the whole system to a halt, and remote & console logins become impossible while samba is running. I don't believe this is a case of too many users trying to connect, as only 2 workstations have been using the samba connectivity, so upping the connection limit in local.h doesn't sound like it would really fix the problem (a solution discovered via google). Appreciate any help here - more info (like the smb.conf) availabe if needed. _________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/
On Fri, 2005-09-23 at 12:04 -0400, Rusty Shackleford wrote:> OS: RHE 3, kernal 2.4.21-32.0.1EL > Samba version: samba-3.0.20 > > Removed RHE version of samba and compiled/installed samba-3.0.20. After > running about 30-60 minutes, I get the following syslog msg: > > "winbindd: Exceeding 200 client connections, no idle connection found" > > Eventually this grinds the whole system to a halt, and remote & console > logins become impossible while samba is running. > > I don't believe this is a case of too many users trying to connect, as only > 2 workstations have been using the samba connectivity, so upping the > connection limit in local.h doesn't sound like it would really fix the > problem (a solution discovered via google). > > Appreciate any help here - more info (like the smb.conf) availabe if needed.Can you try Samba 3.0.20a? A possible (but not verified) explanation is that connections are not being marked as idle in winbindd, when perhaps they should be. Otherwise, make sure to file this on bugzilla.samba.org. (Winbindd had a major rewrite in 3.0.20, and the a release cleans up a number of issues found in the field). Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Samba Developer, SuSE Labs, Novell Inc. http://suse.de Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20051003/6e3a8b96/attachment.bin