Already been down that path. I can't find a network issue anywhere.
Our samba server itself is set up with a bonded interface which attaches
to 2 different cards in the switch. I've pulled each ethernet cable to
see the results and there is no ping loss or interruption of any sort
and shutting down the port at the logical level I see the same result.
I monitor all of the switches and routers in our network with opennms
and cannot find there, or in any of the logs any network interruption
anywhere. Additionally samba seems to be the only server affected. We
have 50 or so linux servers on the network that aren't experiencing any
file server interruption. As for the samba server itself, I moved some
clients over to our backup and the problem follows them.
Sincerely,
Doug Tucker
On 10/03/2013 12:11 PM, Jeremy Allison wrote:
On Thu, Oct 03, 2013 at 12:03:39PM -0500, Doug Tucker wrote:
I see a lot of this in the logs, but can't determine if it really
means anything:
Oct 2 09:45:28 agentsmith2 smbd[21954]: getpeername failed. Error
was Transport endpoint is not connected
Oct 2 09:45:28 agentsmith2 smbd[25948]: write_data: write failure
in writing to client 129.119.104.44. Error Connection reset by peer
Oct 2 09:45:28 agentsmith2 smbd[25971]: write_data: write failure
in writing to client 129.119.105.246. Error Connection reset by peer
Oct 2 09:45:28 agentsmith2 smbd[25883]: write_data: write failure
in writing to client 129.119.103.96. Error Connection reset by peer
Oct 2 09:45:28 agentsmith2 smbd[25987]: getpeername failed. Error
was Transport endpoint is not connected
Oct 2 09:45:28 agentsmith2 smbd[25988]: getpeername failed. Error
was Transport endpoint is not connected
Oct 2 09:45:28 agentsmith2 smbd[25986]: getpeername failed. Error
was Transport endpoint is not connected
Oct 2 09:45:29 agentsmith2 smbd[25985]: getpeername failed. Error
was Transport endpoint is not connected
Oct 2 09:45:29 agentsmith2 smbd[25989]: getpeername failed. Error
was Transport endpoint is not connected
Oct 2 09:45:29 agentsmith2 smbd[25704]: write_data: write failure
in writing to client 129.119.105.119. Error Broken pipe
Oct 2 09:45:29 agentsmith2 smbd[21702]: write_data: write failure
in writing to client 129.119.105.139. Error Connection reset by peer
All this is saying is that the client disconnected - smbd doesn't
know why. I'd start suspecting a network failure somewhere. Check
switches, cables and other hardware.
Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
