thr3ads.net - samba - [Samba] Connection reset by peer [Dec 2004]

If this information is useful, please help other people find it:
Share via:

john.debella@teradyne.com

2004-Dec-24 01:26 UTC

[Samba] Connection reset by peer

Hi,

We continuously see these errors in our logs. I've done some searches on 
this but nothing seems to point to anything specific.

Any ideas?

-John


Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
lib/util_sock.c:get_peer_addr(1000) 
Dec 23 20:14:41 valhalla smbd[3574]:   getpeername failed. Error was 
Transport endpoint is not connected 
Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
lib/util_sock.c:get_peer_addr(1000) 
Dec 23 20:14:41 valhalla smbd[3574]:   getpeername failed. Error was 
Transport endpoint is not connected 
Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
lib/util_sock.c:write_socket_data(430) 
Dec 23 20:14:41 valhalla smbd[3574]:   write_socket_data: write failure. 
Error = Connection reset by peer 
Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
lib/util_sock.c:write_socket(455) 
Dec 23 20:14:41 valhalla smbd[3574]:   write_socket: Error writing 4 bytes 
to socket 5: ERRNO = Connection reset by peer

Thomas M. Skeren III

2004-Dec-24 01:40 UTC

head link

[Samba] Connection reset by peer

john.debella@teradyne.com wrote:
What are you doing?  What configuration.  What network configuration? 
>Hi,
>
>We continuously see these errors in our logs. I've done some searches on
>this but nothing seems to point to anything specific.
>
>Any ideas?
>
>-John
>
>
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:get_peer_addr(1000) 
>Dec 23 20:14:41 valhalla smbd[3574]:   getpeername failed. Error was 
>Transport endpoint is not connected 
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:get_peer_addr(1000) 
>Dec 23 20:14:41 valhalla smbd[3574]:   getpeername failed. Error was 
>Transport endpoint is not connected 
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:write_socket_data(430) 
>Dec 23 20:14:41 valhalla smbd[3574]:   write_socket_data: write failure. 
>Error = Connection reset by peer 
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:write_socket(455) 
>Dec 23 20:14:41 valhalla smbd[3574]:   write_socket: Error writing 4 bytes 
>to socket 5: ERRNO = Connection reset by peer 
>  
>

john.debella@teradyne.com

2004-Dec-24 02:04 UTC

head link

[Samba] Connection reset by peer

Hi Tom,

This particular server is running samba 3.0.7-1.3E.1 on RH 3.0. The domain 
is running AD in mixed mode, (I'll include the smb.conf below), and I 
believe the Windows server is Windows 2003.

Our clients are a mix of Win2k and WinXp. The server is running Clearcase 
and the clients access the Vobs via Samba. They are primarily running 
snapshot views.

We have had several issues come up over the last few weeks, 
(coincidentally when the domain was migrated to Windows AD). The most 
recent are intermittent problems when "password server not available" 
shows up in the logs and these particular errors show up, (connection 
reset by peer... etc...). We recently received a report from a user that 
he/she will get incomplete snapshot view updates, and/or the update 
operation itself runs very slowly. During the incomplete view updates the 
user will get messages like "can't open input file" from
Clearcase.

We're thinking that there is some sort of authentication problem 
happening, however, we haven't been able to determine what has been 
causing all of these problems which are mainly intermittent. I'm hoping 
that by understanding what is causing these connections errors we'll get 
to root cause on the others as well.

One thing to note, we are also running Samba 2.2.7a on a few RedHat 9 
servers which are also running Clearcase. These servers are experiencing 
the same exact issues and are getting the same errors....... These 
machines have been running with this config for over 1 year and have not 
had any problems until recently.

[global]
   workgroup = ICD
   netbios name = VALHALLA
   security = domain
   password server = seneca
   wins server = 131.101.17.18 131.101.17.61
   server string = Linux ClearCase Server %v %h
   log file = /var/log/samba/%m.log
   log level = 6
   max log size = 4000
   username map = /etc/samba/smbusers
   read raw = no
   oplocks = no
   kernel oplocks = no
   level2 oplocks = no
   create mask = 0774
   directory mask = 0775
   map archive = No
   preserve case = yes
   dont descend = /view
   deadtime = 0
   strict locking = no
   domain master = no
   preferred master = no

[vobs]
   path = /export/vobs
   browsable = yes
   writable = yes
   public = yes
   comment = "Vobs"
   csc policy = disable

"Thomas M. Skeren III" <tms3@fskklaw.com>
12/23/2004 08:39 PM

        To:     john.debella@teradyne.com
        cc:     samba@samba.org
        Subject:        Re: [Samba] Connection reset by peer

john.debella@teradyne.com wrote:
What are you doing?  What configuration.  What network configuration? 
>Hi,
>
>We continuously see these errors in our logs. I've done some searches on
>this but nothing seems to point to anything specific.
>
>Any ideas?
>
>-John
>
>
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:get_peer_addr(1000) 
>Dec 23 20:14:41 valhalla smbd[3574]:   getpeername failed. Error was 
>Transport endpoint is not connected 
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:get_peer_addr(1000) 
>Dec 23 20:14:41 valhalla smbd[3574]:   getpeername failed. Error was 
>Transport endpoint is not connected 
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:write_socket_data(430) 
>Dec 23 20:14:41 valhalla smbd[3574]:   write_socket_data: write failure. 
>Error = Connection reset by peer 
>Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0] 
>lib/util_sock.c:write_socket(455) 
>Dec 23 20:14:41 valhalla smbd[3574]:   write_socket: Error writing 4 
bytes >to socket 5: ERRNO = Connection reset by peer 
> 
>

Michael Lueck

2004-Dec-24 12:16 UTC

head link

[Samba] Re: Connection reset by peer

I had some of those showing up on a test network with home-made LAN cables. I
switched it to pre-fab tested onces and the errors went away. So, one vote for
LAN cable issues. Connection resets are a
TCP/IP stack condition you could pick up the existance of with a sniffer, Samba
in my opinion is being nice and logging that it detected it happening.

-- 
Michael Lueck
Lueck Data Systems

Remove the upper case letters NOSPAM to contact me directly.

John Mazza

2004-Dec-24 15:09 UTC

head link

[Samba] Re: Connection reset by peer

I agree.  This indicates a packet loss on the LAN. I would check the cables and
switches.  If you can, try using a
10,000 packet flood ping from the server to a suspect host, with a 1500=byte
packet size.  This is a nice quick test
of network health.  Oh - a bad NIC at either end can also do this.

On Fri, 24 Dec 2004 07:15:52 -0500, Michael Lueck wrote:
>I had some of those showing up on a test network with home-made LAN cables.
I switched it to pre-fab tested oncesand the errors went away. So, one vote for LAN cable issues. Connection resets
are a >TCP/IP stack condition you could pick up the existance of with a sniffer,
Samba in my opinion is being nice and
logging that it detected it happening.>
>-- 
>Michael Lueck
>Lueck Data Systems
>
>Remove the upper case letters NOSPAM to contact me directly.
>
>-- 
>To unsubscribe from this list go to the following URL and read the
>instructions:  https://lists.samba.org/mailman/listinfo/samba

Possibly Parallel Threads

Search for more possibly parallel threads

samba - Dec 2004 - Connection reset by peer

[Samba] Connection reset by peer

[Samba] Connection reset by peer

[Samba] Connection reset by peer

[Samba] Re: Connection reset by peer

[Samba] Re: Connection reset by peer

Possibly Parallel Threads