Error Writing 4 Bytes To Client
[ thread ] [ subject ] [ author ] Hello, I've experienced problem with samba 2.2.x. The server refuses clients and logs: write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe After searching archives I found that it is often mentioned problem and usual reply is: make your network faster / performance-tune your server. It seemed weird to me as I don't expect samba to be so poor baby. And I've seen the same problem at three sites where it worked before. I found very simple cure. Install named at local server/network and estabilish reverse mapping (in-addr.arpa) for IPs in your local net. It seems that samba resolves client's address into name and when it take too long Windows disconnects meanwhile. My problems were caused by using samba on private ip range and problems started when ISP's nameserver stopped to reverse-resolve there IPs. At all my three problematic sites named cured the problem. I used reverse maping which has no PTRs for private range so that named replies NXDOMAIN - but it is enough: it replies fast. I didn't found this info in manuals and I think that is should be mentioned in FAQ. It could help mane confused users. Thanks for Samba being here. Keep good work. Martin Devera aka devik Previous message: SAMBA and Active Directory Next message: Error writing 4 bytes solution - FAQ issue Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the samba mailing list
and earlier Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked Blutech Level 1 (0 points) Q: Samba Errors I am stuck, please help!I have a PC running Windows XP Professional Media Center. It has been connected to the network for about a year. No update to the server has been done https://lists.samba.org/archive/samba/2002-January/035417.html since 8/4/07 and this service stopped working correctly last week. Our mapped network drives are no longer accessible. I have confirmed that all the setting are correct with the PC and with the Windows Service on the Mac XServe. While looking into the log files for the Windows Service https://discussions.apple.com/thread/1099472?start=0&tstart=0 I noticed these entries:[2007/08/23 18:36:54, 0] pdbods.c:odssamgetsampwnam(2329) odssam_getsampwnam: [0]getsam_recordattributes dsRecTypeStandard:Users no account for 'BLUFISHDESIGN'![2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:get_peeraddr(1016) getpeername failed. Error was Socket is not connected[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:write_socketdata(446) writesocketdata: write failure. Error = Broken pipe[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:writesocket(471) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe[2007/08/23 18:46:22, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:sendsmb(663) Error writing 4 bytes to client. -1. (Broken pipe)[2007/08/23 19:22:36, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:read_socketdata(400) readsocketdata: recv failure for 4. Error = Connection reset by peer[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:get_peeraddr(1016) getpeername failed. Error was Socket is not connected[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:get_peeraddr(1016) getpeername failed. Error was Socket is not connected[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:write_socketdata(446) writesocketdata: write failure. Error = Broken pipe[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:writesocket(471) write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe[2007/08/23 19:28:39, 0] /SourceCache/samba/samba-100.9/samba/source/lib/utilsock.c:sendsmb(663) Error writing 4 bytes to client. -1. (Broken pipe)[2007/08/24 10:50:46, 1] /SourceCache/samba/samba-100.9/samba/source/smbd/server.c:opensocketssmbd(359) Reloading services after SIGHUP[2007/08/24 10:59:40,
smbd[2372]: [2007/02/05 01:20:44, 0] lib/util_sock.c:get_peer_addr(1229) Feb 5 01:20:44 Server smbd[2372]: getpeername failed. Error was Transport endpoint is http://forums.fedoraforum.org/archive/index.php/t-146706.html not connected Feb 5 01:20:44 Server smbd[23780]: [2007/02/05 01:20:44, 0] http://lime-technology.com/forum/index.php?topic=345.5;wap2 lib/util_sock.c:get_peer_addr(1229) Feb 5 01:20:44 Server smbd[23780]: getpeername failed. Error was Transport endpoint is not connected Feb 5 01:20:44 Server smbd[23780]: [2007/02/05 01:20:44, 0] lib/util_sock.c:write_data(562) Feb 5 01:20:44 Server smbd[23780]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by error writing peer Feb 5 01:20:44 Server smbd[23780]: [2007/02/05 01:20:44, 0] lib/util_sock.c:send_smb(769) Feb 5 01:20:44 Server smbd[23780]: Error writing 4 bytes to client. -1. (Connection reset by peer) Feb 5 01:20:56 Server smbd[23781]: [2007/02/05 01:20:56, 0] lib/util_sock.c:write_data(562) Feb 5 01:20:56 Server smbd[23781]: write_data: write failure in writing to client 192.168.1.64. Error Connection reset by error writing 4 peer Feb 5 01:20:56 Server smbd[23781]: [2007/02/05 01:20:56, 0] lib/util_sock.c:send_smb(769) Feb 5 01:20:56 Server smbd[23781]: Error writing 4 bytes to client. -1. (Connection reset by peer) Feb 5 01:21:06 Server smbd[23785]: [2007/02/05 01:21:06, 0] lib/util_sock.c:write_data(562) Feb 5 01:21:06 Server smbd[23785]: write_data: write failure in writing to client 192.168.1.64. Error Connection reset by peer Feb 5 01:21:06 Server smbd[23785]: [2007/02/05 01:21:06, 0] lib/util_sock.c:send_smb(769) Feb 5 01:21:06 Server smbd[23785]: Error writing 4 bytes to client. -1. (Connection reset by peer) Feb 5 01:21:18 Server smbd[23788]: [2007/02/05 01:21:18, 0] lib/util_sock.c:write_data(562) Feb 5 01:21:18 Server smbd[23788]: write_data: write failure in writing to client 192.168.1.64. Error Connection reset by peer Feb 5 01:21:18 Server smbd[23788]: [2007/02/05 01:21:18, 0] lib/util_sock.c:send_smb(769) Feb 5 01:21:18 Server smbd[23788]: Error writing 4 bytes to client. -1. (Connection reset by peer) Feb 5 01:21:30 Server smbd[2372]: [2007/02/05 01:21:30, 0] lib/util_sock.c:get_peer_addr(1229) Feb 5 01:21:30 Server smbd[2372]: getpeername failed. Error was Transport endpoint is not c
to finish. The only thing that seems suspect so far are a bunch of Jan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:get_peer_addr(1000)Jan 3 15:39:12 Tower smbd[1339]: getpeername failed. Error was Transport endpoint is not connectedJan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:get_peer_addr(1000)Jan 3 15:39:12 Tower smbd[1339]: getpeername failed. Error was Transport endpoint is not connectedJan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:write_socket_data(430)Jan 3 15:39:12 Tower smbd[1339]: write_socket_data: write failure. Error = Connection reset by peerJan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:write_socket(455)Jan 3 15:39:12 Tower smbd[1339]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer........(many more)I'll send you the whole syslog when parity check completes. dstroot: I upgraded my power supply and re-seated the cables - no errors now for weeks. limetech: --- Quote from: WannaTheater on January 03, 2007, 03:57:08 AM ---Scratch that last question... I never realized you could COPY and PASTE within a command window. I'm still waiting for the parity check to finish. The only thing that seems suspect so far are a bunch of Jan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:get_peer_addr(1000)Jan 3 15:39:12 Tower smbd[1339]: getpeername failed. Error was Transport endpoint is not connectedJan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:get_peer_addr(1000)Jan 3 15:39:12 Tower smbd[1339]: getpeername failed. Error was Transport endpoint is not connectedJan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:write_socket_data(430)Jan 3 15:39:12 Tower smbd[1339]: write_socket_data: write failure. Error = Connection reset by peerJan 3 15:39:12 Tower smbd[1339]: [2007/01/03 15:39:12, 0] lib/util_sock.c:write_socket(455)Jan 3 15:39:12 Tower smbd[1339]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer........(many more)I'll send you the whole syslog