Error Writing 4 Bytes To Client 1 Broken Pipe
Tue, 9 Jan 2001 23:03:48 UTC Severity: normal Found in version 2.0.7-3 Done: Steve Langasek
[ 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 https://bugs.debian.org/81717 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 https://lists.samba.org/archive/samba/2002-January/035417.html 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
hello everybody. i'm a newbie in linux and therefor in samba too, but already got some sort of problem: my machine is running perfectly, samba is working perfectly, http://marc.info/?l=samba&m=101415395413152&w=4 but always in a period of about 10 days "samba" (or what else?) doesn't work anymore. if i try to connect to the shares on the linux-machine i get a timeout error https://ubuntuforums.org/archive/index.php/t-2214449.html in windows. in the /var/log/samba -file i've seen this error: "write_socket_data: write failure. Error = Broken pipe" (more of the log is at the bottom of the message). now someone told me error writing that this error (broken pipe) is a clear signal that the ethernet device is out of order (or another hardware defect; hub, cable).... can you confirm this ? or might it be something else ? the (little bit more detailed) symptoms are: - periodically the shares can't be reached (timeout error in windows). this happens every 10 - 15 days - pinging the machine is error writing 4 no problem - trying to log on to the machine via ssh gets a lot of timeout errors, but if i can log in once, everything works fine (no broken connections, no lag) - restarting samba (using './samba restart') doesn't help - rebooting the server helps (but is a very "nasty" solution) - everything is on a 100mbit lan i hope i've included the important information, if you need more infos please tell me. greetz elias gerber [sorry for my bad english - i hope you understand what i tried to tell you ;( ] little bit more from the log file comes here ('/var/log/samba'): [2002/02/19 19:09:32, 1] lib/util_sock.c:client_name(1007) Gethostbyaddr failed for 192.168.0.20 [2002/02/19 19:09:32, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2002/02/19 19:09:32, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2002/02/19 19:09:32, 0] lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting [2002/02/19 19:09:42, 1] lib/util_sock.c:client_name(1007) Gethostbyaddr failed for 192.168.0.20 [2002/02/19 19:09:42, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2002/02/19 19:09:42, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2002/02/19 19:09:42, 0] lib/uti
2014, 02:05 PMHello, Recently I've updated my Ubuntu fileserver to the latest kernel and removed all older ones (/boot dir was 100% used). Now however, samba does allow me to browse, yet not to open/download files. I've encountered many errors and tried to fix them. Currently I don't see any useful errors anymore, while the problem still exists. The server functions as some sort of proxy, i.e. I have two servers, one with a 2TB disk and its own sabma setup (this server works excellent) and a second small server (512MB ram, 1GB disk, 1cpu) that uses the 2TB disk via NFS and does allow exploring, but not downloading... The server is running Ubuntu 10.0404 LTS, kernel 2.6.32-56-server The NFS disk is mounted via: mount -t nfs -o rw,defaults,nfsvers=3 xxx.xxx.xxx.xxx:/media/Data/someName /media/someName Using command line, I can easily open any file on the mounted NFS disk, from which I conclude that the mount should not be the problem. The configuration file /etc/samba/smb.conf: [global] workgroup = someName server string = someName Fileserver update encrypted = Yes allow trusted domains = No username map = /etc/samba/smbusers log file = /var/log/samba/log.%m max log size = 50 dns proxy = No create mask = 2664 force create mode = 2664 directory mask = 2775 force directory mode = 2775 case sensitive = No access based share enum = Yes [A - Algemeen] comment = A - Algemeen path = /media/someName/A-Algemeen valid users = user1, user2 read only = No The users shown "exist" and logging in from a windows machine to the server does work (for all users). I found quite some errors like thisone: posix_fcntl_getlock: WARNING: lock request at offset 655360, length 61440 returned for which I added posix locking = no to the global region of the config Another frequently occurring error is: write_data: write failure in writing to client 0.0.0.0. Error Broken pipe for which I added (not sure if it is correct) smb ports = 445 Taking a look at the last edited log file, it contains this: [2014/04/01 14:51:51, 0] lib/util_sock.c:1498(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected Error writing 39 bytes to client. -1. (Transport endpoint is not connected) write_data: write failure in writing to client 0.0.0.0. Error Broken pipe [2014/04/01 14:51:51, 0] lib/util_sock.c:743(write_data) [2014/04/01 14:51:51, 0] smbd/process.c:62(srv_send_smb) [2014/04/01 1