How to increase the number of winbindd max connections in samba3x?

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux
  • samba3x-3.3.8-0.51.el5_5
  • samba3x-common-3.3.8-0.51.el5_5
  • samba3x-winbind-3.3.8-0.51.el5_5

Issue

  • Using samba3x-3.3.8-0.51.el5 in a server that receives a lot of simultaneous connections you often can see the following messages in /var/log/samba/log.winbindd. How to prevent this error?

    [2011/04/04 16:14:19,  0] winbindd/winbindd.c:process_loop(950)
  winbindd: Exceeding 200 client connections, no idle connection found

Resolution

  • In samba3x-3.3.8-0.51.el5 and below the number of winbindd max connections are hard coded and fixed to 200.

  • To solve the problem, the new version of samba3x shipped with RHEL 5.6 (samba3x-3.5.4-0.70.el5) implements an option to let user set winbindd max connections defining it in smb.conf, as we can we in documentation:

    # man smb.conf

 winbind max clients (G)
           This parameter specifies the maximum number of clients the winbindd(8) daemon can connect with.
           Default: winbind max clients = 200

  • All versions of RHEL6/RHEL7 can use same fix of adding parameter manually in /etc/samba/smb.conf to fix this issue.

               winbind max clients = 600

  • Restart all required services

               # service smb restart
           # service winbind restart

  • More details about the request to include this parameter are documented in:

     Bug 641379 - Change the limit of winbindd clients dynamically (just to check history about this solution)

     https://bugzilla.redhat.com/show_bug.cgi?id=641379

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments