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