[Samba] client hangs

[Doug Tucker]

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
Oct  2 09:45:29 agentsmith2 smbd[21954]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:write_data(568)
Oct  2 09:45:29 agentsmith2 smbd[25948]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:send_smb(767)
Oct  2 09:45:29 agentsmith2 smbd[25971]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:send_smb(767)
Oct  2 09:45:29 agentsmith2 smbd[25883]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:send_smb(767)
Oct  2 09:45:29 agentsmith2 smbd[25987]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:get_peer_addr(1232)
Oct  2 09:45:29 agentsmith2 smbd[25988]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:get_peer_addr(1232)
Oct  2 09:45:29 agentsmith2 smbd[25986]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:get_peer_addr(1232)
Oct  2 09:45:29 agentsmith2 smbd[25985]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:get_peer_addr(1232)
Oct  2 09:45:29 agentsmith2 smbd[25989]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:get_peer_addr(1232)
Oct  2 09:45:29 agentsmith2 smbd[25704]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:send_smb(767)
Oct  2 09:45:29 agentsmith2 smbd[21702]: [2013/10/02 09:45:29, 0] 
lib/util_sock.c:send_smb(767)
Oct  2 09:45:29 agentsmith2 smbd[21954]:   write_data: write failure in 
writing to client 129.119.103.85. Error Connection reset by peer
Oct  2 09:45:29 agentsmith2 smbd[25948]:   Error writing 60 bytes to 
client. -1. (Connection reset by peer)
Oct  2 09:45:29 agentsmith2 smbd[25971]:   Error writing 60 bytes to 
client. -1. (Connection reset by peer)
Oct  2 09:45:29 agentsmith2 smbd[25883]:   Error writing 60 bytes to 
client. -1. (Connection reset by peer)
Oct  2 09:45:29 agentsmith2 smbd[25987]:   getpeername failed. Error was 
Transport endpoint is not connected
Oct  2 09:45:29 agentsmith2 smbd[25988]:   getpeername failed. Error was 
Transport endpoint is not connected
Oct  2 09:45:29 agentsmith2 smbd[25986]:   getpeername failed. Error was 
Transport endpoint is not connected
Oct  2 09:45:30 agentsmith2 smbd[25985]:   getpeername failed. Error was 
Transport endpoint is not connected
Oct  2 09:45:30 agentsmith2 smbd[25989]:   getpeername failed. Error was 
Transport endpoint is not connected

Sincerely,

Doug Tucker

On 10/03/2013 11:11 AM, Doug Tucker wrote:
> Virus scanning was one of the early suspects.  For no real reason 
> though as nothing had changed.  The macs and linux clients though are 
> affected and neither have virus software installed.
>
> That's a huge frustrating point about it.  It's is completely and 
> wildly random.  I can't reproduce it at all, I can only see it when it 
> happens if someone calls and I run down there really quick.  The only 
> common thing being that when it's happening to 1, it's happening to 
> all.  And during the time it takes to reboot, it probably would have 
> cleared up anyway.
>
> Yesterday during a bad hang a user called, so I immediately tried to 
> smbmount my home directory (I usually just have it mounted) and it 
> hung for quite a while, then returned "resource unavailable". The 
> server seemed completely fine though.  About 2 minutes later after the 
> caller said it cleared up I was able to mount it. Looking at the 
> server everything seemed fine.  I could ping the server.  I could 
> telnet to 139 and 445, so they were listening. Load was less than 1.  
> The file server seemed fine.  Communication between the 2 was fine.  
> It seems like an internal issue with samba somehow but samba itself 
> hasn't been updated since this started happening (it was already at 
> the latest version for the distro).
>
> Sincerely,
>
> Doug Tucker
>
> On 10/03/2013 11:00 AM, Klaus Hartnegg wrote:
>> On 03.10.2013 17:20, Doug Tucker wrote:
>>> client attempts to access a resource on a
>>> shared drive either by saving, or just simply clicking on a folder on
>>> the shared drive can takes minutes to complete.
>>
>> Is it reproducable by clicking the same folder again after rebooting 
>> the client?
>>
>> Do you have the same antivirus software on Win and Mac? I've seen 
>> such behaviour years ago after an antivirus update when accessing a 
>> remote directory with a certain powerpoint file in it, that suddenly 
>> took minutes to scan. The scan can take place already when going into 
>> that directory, even when not clicking on the specific file.
>>
>> Klaus
>>
>