Re: [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 pipe Where 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-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [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 Teamhttp://samba.org Private repo http://git.samba.org/?p=mat/samba.git;a=summary -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Winbindd filling log file with ' final write to client failed: Broken pipe'
Hello Volker, thank for your reply! Where is the real error here? This seems completely normal to me with such a high debug level. The error I'm referring to is: [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 I can of course disregard it but I would still be wondering why it fails writing to the client :) Have a nice day, Gabriele -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Winbindd filling log file with ' final write to client failed: Broken pipe'
On Fri, Apr 01, 2011 at 09:25:30AM +0200, Gabriele Paggi wrote: Hello Volker, thank for your reply! Where is the real error here? This seems completely normal to me with such a high debug level. The error I'm referring to is: [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 I can of course disregard it but I would still be wondering why it fails writing to the client :) Oh, that's in response to a Solaris bug. Instead of just closing the socket we write one byte before closing it. The bug was that the winbind client did not get a 0 read size when we just close the server end of a unix domain socket and thus went into a timeout. Without this bug it can happen that we can't write to that socket anymore, but it's very hard to detect at runtime whether we have this bug. So we live with this error message. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
