Gabriele Paggi
2011-Mar-31 19:08 UTC
[Samba] Winbindd filling log file with " final write to client failed: Broken pipe"
Hello, I've set up winbindd to authenticate local users against our active directory servers and everything works fine. I see plenty of the following lines in my logs and I'm wondering if someone can help me troubleshooting this: [2011/03/31 15:15:02, 10] winbindd/winbindd_cache.c:cache_retrieve_response(2666) Retrieving response for pid 8749 [2011/03/31 15:15:02, 7] winbindd/winbindd_idmap.c:winbindd_sid2gid_async(351) winbindd_sid2gid_async: Resolving S-1-5-21-2615388863-3808077908-615857747-2195 to a gid [2011/03/31 15:15:02, 10] winbindd/winbindd_dual.c:async_request(125) Sending request to child pid 8749 (domain='') [2011/03/31 15:15:02, 10] winbindd/winbindd_cache.c:cache_retrieve_response(2666) Retrieving response for pid 8749 [2011/03/31 15:15:02, 2] winbindd/winbindd.c:remove_client(744) final write to client failed: Broken pipe [2011/03/31 15:15:02, 2] winbindd/winbindd.c:remove_client(744) final write to client failed: Broken pipe Researches on the internet didn't help as this kind of error are always associated with some functionality not working at all, but that's not my case (apparently). Versions: OS: RHEL 5.5 smbd: Version 3.3.8-0.52.el5_5 winbind: Version 3.3.8-0.52.el5_5 This is my smb.conf: [global] workgroup = XXX password server = YYY, ZZZ realm = XXX.KKK.NET security = ads template homedir = /home/%U template shell = /bin/bash winbind use default domain = true winbind offline logon = true winbind cache time = 120 #log level = 0 winbind:10 ldap connection timeout = 2 ldap timeout = 2 keepalive = 300 load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes client schannel = auto allow trusted domains = no idmap uid = 33554432 - 4294967295 idmap gid = 33554432 - 4294967295 idmap config XXX : default = yes idmap config XXX : backend = rid idmap config XXX : range = 1000 - 33554431 idmap cache time = 604800 Any help is, of course, highly appreciated :) Cheers, Gabriele
Volker Lendecke
2011-Apr-01 06:32 UTC
[Samba] Winbindd filling log file with " final write to client failed: Broken pipe"
On Thu, Mar 31, 2011 at 09:08:12PM +0200, Gabriele Paggi wrote:> I've set up winbindd to authenticate local users against our active > directory servers and everything works fine. > I see plenty of the following lines in my logs and I'm wondering if > someone can help me troubleshooting this: > > [2011/03/31 15:15:02, 10] > winbindd/winbindd_cache.c:cache_retrieve_response(2666) > Retrieving response for pid 8749 > [2011/03/31 15:15:02, 7] > winbindd/winbindd_idmap.c:winbindd_sid2gid_async(351) > winbindd_sid2gid_async: Resolving > S-1-5-21-2615388863-3808077908-615857747-2195 to a gid > [2011/03/31 15:15:02, 10] winbindd/winbindd_dual.c:async_request(125) > Sending request to child pid 8749 (domain='') > [2011/03/31 15:15:02, 10] > winbindd/winbindd_cache.c:cache_retrieve_response(2666) > Retrieving response for pid 8749 > [2011/03/31 15:15:02, 2] winbindd/winbindd.c:remove_client(744) > final write to client failed: Broken pipe > [2011/03/31 15:15:02, 2] winbindd/winbindd.c:remove_client(744) > final write to client failed: Broken pipeWhere is the real error here? This seems completely normal to me with such a high debug level. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen
Matthieu Patou
2011-Apr-01 06:57 UTC
[Samba] Winbindd filling log file with " final write to client failed: Broken pipe"
On 31/03/2011 23:08, Gabriele Paggi wrote:> Hello, > > I've set up winbindd to authenticate local users against our active > directory servers and everything works fine. > I see plenty of the following lines in my logs and I'm wondering if > someone can help me troubleshooting this: > > [2011/03/31 15:15:02, 10] > winbindd/winbindd_cache.c:cache_retrieve_response(2666) > Retrieving response for pid 8749 > [2011/03/31 15:15:02, 7] > winbindd/winbindd_idmap.c:winbindd_sid2gid_async(351) > winbindd_sid2gid_async: Resolving > S-1-5-21-2615388863-3808077908-615857747-2195 to a gid > [2011/03/31 15:15:02, 10] winbindd/winbindd_dual.c:async_request(125) > Sending request to child pid 8749 (domain='') > [2011/03/31 15:15:02, 10] > winbindd/winbindd_cache.c:cache_retrieve_response(2666) > Retrieving response for pid 8749 > [2011/03/31 15:15:02, 2] winbindd/winbindd.c:remove_client(744) > final write to client failed: Broken pipe > [2011/03/31 15:15:02, 2] winbindd/winbindd.c:remove_client(744) > final write to client failed: Broken pipe > > Researches on the internet didn't help as this kind of error are > always associated with some functionality not working at all, but > that's not my case (apparently). >Look to me familiar with a bug that I reported to Gunther and that crashed my server this summer as far as I remember it's fixed in 3.5.x. Gunther can you confirm ? -- Matthieu Patou Samba Team http://samba.org Private repo http://git.samba.org/?p=mat/samba.git;a=summary