Samba hanging of FC3.

WipeOut wipe_out at users.sourceforge.net
Wed Nov 17 11:35:27 UTC 2004


WipeOut wrote:

> I have the firewall disabled so its not that..
> Thanks for trying..
>
Continuing on with thios problem I am getting the folowing showing in 
the log on the samba server..

Nov 17 07:15:15 nasfs01 smbd[23737]: [2004/11/17 07:15:15, 0] lib/util_sock.c:get_peer_addr(1000) 
Nov 17 07:15:15 nasfs01 smbd[23737]:   getpeername failed. Error was Transport endpoint is not connected 
Nov 17 07:15:15 nasfs01 smbd[23737]: [2004/11/17 07:15:15, 0] lib/util_sock.c:get_peer_addr(1000) 
Nov 17 07:15:15 nasfs01 smbd[23737]:   getpeername failed. Error was Transport endpoint is not connected 
Nov 17 07:15:15 nasfs01 smbd[23737]: [2004/11/17 07:15:15, 0] lib/util_sock.c:write_socket_data(430) 
Nov 17 07:15:15 nasfs01 smbd[23737]:   write_socket_data: write failure. Error = Connection reset by peer 
Nov 17 07:15:15 nasfs01 smbd[23737]: [2004/11/17 07:15:15, 0] lib/util_sock.c:write_socket(455) 
Nov 17 07:15:15 nasfs01 smbd[23737]:   write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer 
Nov 17 07:15:15 nasfs01 smbd[23737]: [2004/11/17 07:15:15, 0] lib/util_sock.c:send_smb(647) 
Nov 17 07:15:15 nasfs01 smbd[23737]:   Error writing 4 bytes to client. -1. (Connection reset by peer) 
Nov 17 08:53:43 nasfs01 smbd[23748]: [2004/11/17 08:53:43, 0] lib/util_sock.c:read_socket_data(384) 
Nov 17 08:53:44 nasfs01 smbd[23748]:   read_socket_data: recv failure for 4. Error = Connection reset by peer 
Nov 17 09:50:01 nasfs01 smbd[23752]: [2004/11/17 09:50:01, 0] lib/util_sock.c:read_socket_data(384) 
Nov 17 09:50:01 nasfs01 smbd[23752]:   read_socket_data: recv failure for 4. Error = Connection reset by peer 
Nov 17 10:31:30 nasfs01 smbd[23759]: [2004/11/17 10:31:30, 0] lib/util_sock.c:write_socket_data(430) 
Nov 17 10:31:30 nasfs01 smbd[23759]:   write_socket_data: write failure. Error = Connection reset by peer 
Nov 17 10:31:30 nasfs01 smbd[23759]: [2004/11/17 10:31:30, 0] lib/util_sock.c:write_socket(455) 
Nov 17 10:31:30 nasfs01 smbd[23759]:   write_socket: Error writing 165 bytes to socket 5: ERRNO = Connection reset by peer 
Nov 17 10:31:30 nasfs01 smbd[23759]: [2004/11/17 10:31:30, 0] lib/util_sock.c:send_smb(647) 
Nov 17 10:31:30 nasfs01 smbd[23759]:   Error writing 165 bytes to client. -1. (Connection reset by peer) 
Nov 17 10:38:11 nasfs01 smbd[23767]: [2004/11/17 10:38:11, 0] lib/util_sock.c:read_socket_data(384) 
Nov 17 10:38:11 nasfs01 smbd[23767]:   read_socket_data: recv failure for 4. Error = Connection reset by peer 
Nov 17 10:38:30 nasfs01 smbd[23769]: [2004/11/17 10:38:30, 0] lib/util_sock.c:read_socket_data(384) 
Nov 17 10:38:30 nasfs01 smbd[23769]:   read_socket_data: recv failure for 4. Error = Connection reset by peer 
Nov 17 11:25:10 nasfs01 smbd[23770]: [2004/11/17 11:25:10, 0] lib/util_sock.c:read_socket_data(384) 
Nov 17 11:25:10 nasfs01 smbd[23770]:   read_socket_data: recv failure for 4. Error = Connection reset by peer 


And this on my PC..

Nov 17 11:23:58 asterix kernel: SMB connection re-established (-5)
Nov 17 11:23:59 asterix kernel: smb_lookup: find //pagefile.sys failed, 
error=-26
Nov 17 11:27:05 asterix kernel: smb_lookup: find //.Trash-root failed, 
error=-512
Nov 17 11:27:05 asterix kernel: smb_lookup: find //.Trash-root failed, 
error=-512
Nov 17 11:27:24 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3220] timed out!
Nov 17 11:27:24 asterix kernel: smb_add_request: request [0d80c980, 
mid=3222] timed out!
Nov 17 11:27:35 asterix kernel: smb_add_request: request [1299d080, 
mid=3244] timed out!
Nov 17 11:27:35 asterix kernel: smb_add_request: request [0d80c880, 
mid=3243] timed out!
Nov 17 11:27:35 asterix kernel: smb_lookup: find //.Trash-root failed, 
error=-5
Nov 17 11:27:38 asterix kernel: smb_add_request: request [1299d380, 
mid=3245] timed out!
Nov 17 11:27:54 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3246] timed out!
Nov 17 11:28:08 asterix kernel: smb_add_request: request [0d80c580, 
mid=3247] timed out!
Nov 17 11:28:24 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3248] timed out!
Nov 17 11:28:45 asterix kernel: smb_add_request: request [0d80c580, 
mid=3249] timed out!
Nov 17 11:28:54 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3250] timed out!
Nov 17 11:29:24 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3251] timed out!
Nov 17 11:29:54 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3252] timed out!
Nov 17 11:30:24 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3253] timed out!
Nov 17 11:30:54 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3254] timed out!
Nov 17 11:31:24 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3255] timed out!
Nov 17 11:31:24 asterix kernel: smb_lookup: find //.Trash-root failed, 
error=-5
Nov 17 11:31:24 asterix kernel: smb_get_length: Invalid NBT packet, code=b3
Nov 17 11:31:54 asterix kernel: smb_add_request: request [0d80cb80, 
mid=3256] timed out!

It seems to be raleted to Nautilus and Samba because when I access the 
Samba shares through a terminal they don't appear to get stuck..

Later..




More information about the fedora-list mailing list