search for: winbindd_listen_fde_handler

...re using NTLM authentication for a number of trusted domains over WAN connections (all 100Mbit fibre links, so shouldn't be considered slow). Recently we've noticed that the winbind connections are exceeding the default 200, as below, [2013/04/16 10:19:15.510056, 0] winbindd/winbindd.c:914(winbindd_listen_fde_handler) winbindd: Exceeding 200 client connections, no idle connection found[2013/04/16 10:19:15.548416, 0] winbindd/winbindd.c:914(winbindd_listen_fde_handler) winbindd: Exceeding 200 client connections, no idle connection found[2013/04/16 10:19:15.548545, 0] winbindd/winbindd.c:914(winbindd_listen_f...

...re using NTLM authentication for a number of trusted domains over WAN connections (all 100Mbit fibre links, so shouldn't be considered slow). Recently we've noticed that the winbind connections are exceeding the default 200, as below, [2013/04/16 10:19:15.510056, 0] winbindd/winbindd.c:914(winbindd_listen_fde_handler) winbindd: Exceeding 200 client connections, no idle connection found[2013/04/16 10:19:15.548416, 0] winbindd/winbindd.c:914(winbindd_listen_fde_handler) winbindd: Exceeding 200 client connections, no idle connection found[2013/04/16 10:19:15.548545, 0] winbindd/winbindd.c:914(winbindd_listen_f...

Smbd: Version 4.1.6-Ubuntu Winbind: Version 4.1.6-Ubuntu root at tank-1:/var/log/samba# tail log.winbindd [2015/02/17 10:13:57.996865, 0] ../source3/winbindd/winbindd.c:1023(winbindd_listen_fde_handler) winbindd: Exceeding 200 client connections, no idle connection found I'm getting above error on the winbind services which are causing several issues such as disconnecting users from active transfers and reprompting user credentials that doesn't accept user info. I found this closed bug...

...7: 52.255050, 0] ../source3/winbindd/winbindd_dual.c:105(child_write_response) Sep 1 09:07:52 ### winbindd [19488]: Could not write result And after several such errors, logging changes to: Sep 1 09:07:53 winbindd ### [3068]: [01/09/2015 09: 07: 53.556980, 0] ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) Sep 1 09:07:53 winbindd ### [3068]: winbindd: Exceeding 800 client connections, the idle connection found In the samba logs (/opt/samba/var) there is no log. The following configuration of smb.conf: # Global parameters [global] workgroup = DOMAIN realm = DOMAIN.COM netbios name = SERVER...

...c:105(child_write_response) Sep 1 09:04:30 wdc winbindd[18757]: Could not write result That repeat as so many times that "winbind max clients = 800" configured. And then changed to: Sep 1 09:08:07 wdc winbindd[3068]: [2015/09/01 09:08:07.980952, 0] ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) Sep 1 09:08:07 wdc winbindd[3068]: winbindd: Exceeding 800 client connections, no idle connection found That repeats so long the samba is up, I needed to stop and start the samba service. Seems that when the first error occurs samba server mantains the client connection, but the client (e.g.:...

...t; Sep 1 09:04:30 wdc winbindd[18757]: Could not write result > > That repeat as so many times that "winbind max clients = 800" > configured.And then changed to: Sep 1 09:08:07 wdc winbindd[3068]: > [2015/09/01 09:08:07.980952, 0] > ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) Sep 1 > 09:08:07 wdc winbindd[3068]: winbindd: Exceeding 800 client > connections, no idle connection found That repeats so long the samba > is up, I needed to stop and start the samba service. > Seems that when the first error occurs samba server mantains the > client connectio...

...source3/winbindd/winbindd_dual.c:105(child_write_response) > Sep 1 09:07:52 ### winbindd [19488]: Could not write result > > And after several such errors, logging changes to: > Sep 1 09:07:53 winbindd ### [3068]: [01/09/2015 09: 07: 53.556980, 0] ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) > Sep 1 09:07:53 winbindd ### [3068]: winbindd: Exceeding 800 client connections, the idle connection found > > In the samba logs (/opt/samba/var) there is no log. > > The following configuration of smb.conf: > # Global parameters > [global] > workgroup = DOMAIN &g...

...../source3/winbindd/winbindd_dual.c:105(child_write_response) > Sep 1 09:07:52 ### winbindd [19488]: Could not write result > > And after several such errors, logging changes to: > Sep 1 09:07:53 winbindd ### [3068]: [01/09/2015 09: 07: 53.556980, 0] ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) > Sep 1 09:07:53 winbindd ### [3068]: winbindd: Exceeding 800 client connections, the idle connection found > > In the samba logs (/opt/samba/var) there is no log. > > The following configuration of smb.conf: > # Global parameters > [global] > workgroup = DOMAIN > realm...

...c:105(child_write_response) Sep 1 09:04:30 wdc winbindd[18757]: Could not write result That repeat as so many times that "winbind max clients = 800" configured. And then changed to: Sep 1 09:08:07 wdc winbindd[3068]: [2015/09/01 09:08:07.980952, 0] ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) Sep 1 09:08:07 wdc winbindd[3068]: winbindd: Exceeding 800 client connections, no idle connection found That repeats so long the samba is up, I needed to stop and start the samba service. Seems that when the first error occurs samba server mantains the client connection, but the client (e.g.:...

...gt; Sep 1 09:04:30 wdc winbindd[18757]: Could not write result > > That repeat as so many times that "winbind max clients = 800" > configured.And then changed to: Sep 1 09:08:07 wdc winbindd[3068]: > [2015/09/01 09:08:07.980952, 0] > ../source3/winbindd/winbindd.c:1116(winbindd_listen_fde_handler) Sep 1 > 09:08:07 wdc winbindd[3068]: winbindd: Exceeding 800 client > connections, no idle connection found That repeats so long the samba > is up, I needed to stop and start the samba service. > Seems that when the first error occurs samba server mantains the > client connecti...