Re: [Samba] diagnosing broken pipe errors
Andrew Bartlett wrote: On Tue, 2008-02-26 at 16:20 -0500, Ernie Buford wrote: I'm hoping to get some guidance diagnosing intermittent smbd errors that have been cropping up in the last 2 months. They are sporadic, difficult to reproduce, and don't reveal much of a pattern so far except that the majority are generated by a couple of clients, although several clients appear to be affected. Typical symptom on the client is a hang when attempting to look at the share in Windows Explorer, or table data suddenly disappears when working in MS Access, or sometimes no symptom at all. It seems the most repeatable error condition is when a drive is first mapped after bootup, but even that is not consistent. I've found some indication via web search that this might be related to network problems, so that's one reason I'm hoping for diagnostic tips. I'm aware of no recent network changes that might be causing this problem, and I've tried the worst-behaving machine on a different ethernet cable and switch port with no improvement. I would replace your network cards and switches with better quality gear, if possible. I'd be more suspicious of the network gear if there were other networking symptoms pointing in that direction, but so far, these samba errors are the only indication that anything is wrong. Other means of pushing data to and from these workstations work fine. We are on a Cisco Catalyst 3650G Series Gigabit switch and use Dell Precision workstations, except for the most error-plagued machine, which is an Optiplex GX620. These aren't exactly cheap, entry-level machines. Still, I'll try to find a way to see if I can isolate the problem to particular NICs or the switch itself (I can fall back to a 100Mb switch that we still have online). Thanks for your input. EB Broken pipe errors should not occour on a LAN, unless the client is rebooted. Multiuser control of MS Access can be a particular pain in this regard, and many network set 'veto oplock files' to exclude *.mdb. This prevents oplocks (which require server-initiated communication) from being granted. The getpeername error may well be harmless, simply due to Windows being silly and connecting to both 139 and 445, then dropping one. Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] diagnosing broken pipe errors
On Tue, 2008-02-26 at 16:20 -0500, Ernie Buford wrote: > I'm hoping to get some guidance diagnosing intermittent smbd > errors that have been cropping up in the last 2 months. They > are sporadic, difficult to reproduce, and don't reveal much of > a pattern so far except that the majority are generated by a > couple of clients, although several clients appear to be > affected. Typical symptom on the client is a hang when > attempting to look at the share in Windows Explorer, or > table data suddenly disappears when working in MS Access, > or sometimes no symptom at all. It seems the most repeatable > error condition is when a drive is first mapped after bootup, > but even that is not consistent. > I've found some indication via web search that this might be > related to network problems, so that's one reason I'm > hoping for diagnostic tips. I'm aware of no recent network > changes that might be causing this problem, and I've tried > the worst-behaving machine on a different ethernet cable > and switch port with no improvement. I would replace your network cards and switches with better quality gear, if possible. Broken pipe errors should not occour on a LAN, unless the client is rebooted. Multiuser control of MS Access can be a particular pain in this regard, and many network set 'veto oplock files' to exclude *.mdb. This prevents oplocks (which require server-initiated communication) from being granted. The getpeername error may well be harmless, simply due to Windows being silly and connecting to both 139 and 445, then dropping one. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] diagnosing broken pipe errors
I'm hoping to get some guidance diagnosing intermittent smbd errors that have been cropping up in the last 2 months. They are sporadic, difficult to reproduce, and don't reveal much of a pattern so far except that the majority are generated by a couple of clients, although several clients appear to be affected. Typical symptom on the client is a hang when attempting to look at the share in Windows Explorer, or table data suddenly disappears when working in MS Access, or sometimes no symptom at all. It seems the most repeatable error condition is when a drive is first mapped after bootup, but even that is not consistent. My situation: 2 Dell Servers running RHEL4 (2.6.9-67.ELsmp) and samba-3.0.25b-1.el4_6.4. These are up2date as of mid-February. I get the errors on both servers. There are about 10 WinXP Pro workstations that map shares from these servers. I've been running Samba on one server for 5+ years and a couple years on the newer one. This is the first time I've seen these errors, and I'm a little worried about data corruption though they've only resulted in some user inconvenience so far (that I can tell). I've found some indication via web search that this might be related to network problems, so that's one reason I'm hoping for diagnostic tips. I'm aware of no recent network changes that might be causing this problem, and I've tried the worst-behaving machine on a different ethernet cable and switch port with no improvement. Here's a typical error: Feb 26 11:24:06 srvr smbd[6424]: [2008/02/26 11:24:06, 0] lib/util_sock.c:read_data(534) Feb 26 11:24:06 srvr smbd[6424]: read_data: read failure for 4 bytes to client 123.444.500.95. Error = Connection timed out Feb 26 11:24:06 srvr smbd[6424]: [2008/02/26 11:24:06, 0] lib/util_sock.c:write_data(562) Feb 26 11:24:06 srvr smbd[6424]: write_data: write failure in writing to client 123.444.500.95. Error Broken pipe Feb 26 11:24:06 srvr smbd[6424]: [2008/02/26 11:24:06, 0] lib/util_sock.c:send_smb(769) Feb 26 11:24:06 srvr smbd[6424]: Error writing 75 bytes to client. -1. (Broken pipe) Here's another: Feb 26 14:02:51 srvr smbd[16467]: [2008/02/26 14:02:51, 0] lib/util_sock.c:get_peer_addr(1232) Feb 26 14:02:51 srvr smbd[16467]: getpeername failed. Error was Transport endpoint is not connected Feb 26 14:02:51 srvr smbd[16467]: [2008/02/26 14:02:51, 0] lib/access.c:check_access(327) Feb 26 14:02:51 srvr smbd[16467]: [2008/02/26 14:02:51, 0] lib/util_sock.c:get_peer_addr(1232) Feb 26 14:02:51 srvr smbd[16467]: getpeername failed. Error was Transport endpoint is not connected Feb 26 14:02:51 srvr smbd[16467]: Denied connection from (0.0.0.0) Feb 26 14:02:51 srvr smbd[16467]: [2008/02/26 14:02:51, 0] lib/util_sock.c:get_peer_addr(1232) Feb 26 14:02:51 srvr smbd[16467]: getpeername failed. Error was Transport endpoint is not connected Feb 26 14:02:51 srvr smbd[16467]: Connection denied from 0.0.0.0 Feb 26 14:02:51 srvr smbd[16467]: [2008/02/26 14:02:51, 0] lib/util_sock.c:write_data(562) Feb 26 14:02:51 srvr smbd[16467]: write_data: write failure in writing to client 123.444.500.117. Error Connection reset by peer Feb 26 14:02:51 srvr smbd[16467]: [2008/02/26 14:02:51, 0] lib/util_sock.c:send_smb(769) Feb 26 14:02:51 srvr smbd[16467]: Error writing 5 bytes to client. -1. (Connection reset by peer) I also see this one, although I'm not sure it's related: Feb 26 09:15:52 srvr smbd[5679]: [2008/02/26 09:15:52, 0] smbd/nttrans.c:call_nt_transact_ioctl(2481) Feb 26 09:15:52 srvr smbd[5679]: call_nt_transact_ioctl(0x9005c): Currently not implemented. Thanks, EB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
