samba - Feb 2005 - smb log error-Transport end point/getpeername

Mates,

    I'm trying to solve some log errors I getting. I have samba 3.0.7 
installed on Suse 9.0. It has been happening intermittently for several 
months. I don't know if this is XP client related or what. Any thoughts: The
errors are:

Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/access.c:check_access(328)
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:00:33 skyline smbd[14408]:   Denied connection from 0.0.0.0 
(0.0.0.0)
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:00:33 skyline smbd[14408]:   Connection denied from 0.0.0.0
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:write_socket_data(430)
Feb  9 20:00:33 skyline smbd[14408]:   write_socket_data: write failure. 
Error = Connection reset by peer
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:write_socket(455)
Feb  9 20:00:33 skyline smbd[14408]:   write_socket: Error writing 5 bytes 
to socket 22: ERRNO = Connection reset by peer
Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] 
lib/util_sock.c:send_smb(647)
Feb  9 20:00:33 skyline smbd[14408]:   Error writing 5 bytes to client. -1. 
(Connection reset by peer)
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:04:07 skyline smbd[14432]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:04:07 skyline smbd[14432]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:04:07 skyline smbd[14432]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/access.c:check_access(328)
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:04:07 skyline smbd[14432]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:04:07 skyline smbd[14432]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:04:07 skyline smbd[14432]:   Denied connection from 0.0.0.0 
(0.0.0.0)
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:get_peer_addr(1000)
Feb  9 20:04:07 skyline smbd[14432]:   getpeername failed. Error was 
Transport endpoint is not connected
Feb  9 20:04:07 skyline smbd[14432]:   Connection denied from 0.0.0.0
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:write_socket_data(430)
Feb  9 20:04:07 skyline smbd[14432]:   write_socket_data: write failure. 
Error = Connection reset by peer
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:write_socket(455)
Feb  9 20:04:07 skyline smbd[14432]:   write_socket: Error writing 5 bytes 
to socket 5: ERRNO = Connection reset by peer
Feb  9 20:04:07 skyline smbd[14432]: [2005/02/09 20:04:07, 0] 
lib/util_sock.c:send_smb(647)
Feb  9 20:04:07 skyline smbd[14432]:   Error writing 5 bytes to client. -1. 
(Connection reset by peer)


--
David C. Rankin, J.D., P.E.
RANKIN LAW FIRM, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankinlawfirm.com
--

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

david rankin wrote:

|
|    I'm trying to solve some log errors I getting. I
| have samba 3.0.7 installed on Suse 9.0. It has been
| happening intermittently for several months. I don't know
| if this is XP client related or what. Any thoughts:
| The errors are:
|
| Feb  9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0]
| lib/util_sock.c:get_peer_addr(1000)
| Feb  9 20:00:33 skyline smbd[14408]:   getpeername failed. Error was
| Transport endpoint is not connected

I know that Windows XP clients try to connect to port
139 and 445 in parallel and drop the connection to port
139 if the connect to 445 is successful.  This is probably
what you are seeing.





cheers, jerry
====================================================================Alleviating
the pain of Windows(tm)      ------- http://www.samba.org
GnuPG Key                ----- http://www.plainjoe.org/gpg_public.asc
"I never saved anything for the swim back."     Ethan Hawk in Gattaca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCC2ZmIR7qMdg1EfYRApRrAKCueTKNLmp2eIpxsDBwXxeTPCPnFwCdFJha
cP0Ftaoy1weqJ3J2SJLYTxw=Rjrf
-----END PGP SIGNATURE-----

better late than never
I would suggest you take a look at the File and Record Locking section 
[http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/locking.html] 
of the samba official howto 
[http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/] (must read 
if you have not ;) ) regarding your database corruption problems

I hope this helps or that you already found your problem