samba - Jul 2009 - Streaming large videos causes server's networking to crash

Greetings all; I really hope someone can help me.  I recently upgraded
to the most recent version (from a year-old version) of Samba, on a
server now running on Ubuntu Server Jaunty Jackalope x64.  After
upgrading, whenever I play large media files on my Vista machine
streamed from the Samba server, the networking functionality on the
server drops out.  Sometimes it happens after playing a video for 2
minutes, sometimes it takes 2 hours.  After it drops out, running
/etc/init.d/networking restart on the local terminal restores networking
functionality.  Rebooting also has this effect.  This never happened
before I upgraded, so I doubt it's a hardware problem.  I see the
following in the log for the computer the video was being viewed on:

[2009/07/29 01:13:21,  0] lib/util_sock.c:write_data(1136)
[2009/07/29 01:13:21,  0] lib/util_sock.c:get_peer_addr_internal(1676)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error
Connection reset by peer
[2009/07/29 01:13:21,  0] smbd/process.c:srv_send_smb(74)
  Error writing 4159 bytes to client. -1. (Transport endpoint is not
connected)
[2009/07/29 01:13:21,  1] smbd/service.c:close_cnum(1323)
  murahime (::ffff:192.168.1.100) closed connection to service Paul's Folder

and the following in log.nmbd:

[2009/07/29 01:13:23,  0]
nmbd/nmbd_become_lmb.c:become_local_master_stage2(395)
  *****

  Samba name server DITE is now a local master browser for workgroup
WORKGROUP on subnet 192.168.1.200

  *****

Any ideas?

--Paul Accisano

Which network device are you using?

when it happens, do a
dmesg|tail
on the server. Anything interesting there?

I had a similar symptoms which turned out to be caused by the Realtek device
on my motherboard and the driver in my Linux distro. (and when I fixed that
by using another driver, my machine was still not stable so I swapped the
motherboard out for an older one - that's when I found I also had a faulty
sata data cable... Just be warned that problems don't always come alone)


2009/7/29 Paul Accisano <shiningmasamune at gmail.com>
> Greetings all; I really hope someone can help me.  I recently upgraded
> to the most recent version (from a year-old version) of Samba, on a
> server now running on Ubuntu Server Jaunty Jackalope x64.  After
> upgrading, whenever I play large media files on my Vista machine
> streamed from the Samba server, the networking functionality on the
> server drops out.  Sometimes it happens after playing a video for 2
> minutes, sometimes it takes 2 hours.  After it drops out, running
> /etc/init.d/networking restart on the local terminal restores networking
> functionality.  Rebooting also has this effect.  This never happened
> before I upgraded, so I doubt it's a hardware problem.  I see the
> following in the log for the computer the video was being viewed on:
>
> [2009/07/29 01:13:21,  0] lib/util_sock.c:write_data(1136)
> [2009/07/29 01:13:21,  0] lib/util_sock.c:get_peer_addr_internal(1676)
>  getpeername failed. Error was Transport endpoint is not connected
>  write_data: write failure in writing to client 0.0.0.0. Error
> Connection reset by peer
> [2009/07/29 01:13:21,  0] smbd/process.c:srv_send_smb(74)
>  Error writing 4159 bytes to client. -1. (Transport endpoint is not
> connected)
> [2009/07/29 01:13:21,  1] smbd/service.c:close_cnum(1323)
>  murahime (::ffff:192.168.1.100) closed connection to service Paul's
Folder
>
> and the following in log.nmbd:
>
> [2009/07/29 01:13:23,  0]
> nmbd/nmbd_become_lmb.c:become_local_master_stage2(395)
>  *****
>
>  Samba name server DITE is now a local master browser for workgroup
> WORKGROUP on subnet 192.168.1.200
>
>  *****
>
> Any ideas?
>
> --Paul Accisano
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

Quoting Dan Grindstaff <dan at oakrun.net>:
> Hello All,
>
> I have set up samba server 3.0.33-0.fc8 and successfully created a share
> accessible by all machines in my workgroup.  When I open up network on my
> linux box I can see all other machines in the workgroup.  I have set up
> other shares on other machines and am able to see them but when I try to
> open the share from linux I get login message. I do not want to have to log
> in from linux.  I have set up the shares on the windows machines to be
> accessible to everyone. TIA for any and all advice.
Well the Linux client behavior probably has little to do with the  
server side.  You might consider providing credentials in /etc/fstab  
and mount the shares that way.

Thanks!

-----Original Message-----
From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
On Behalf Of Jonathon Doran
Sent: Wednesday, July 29, 2009 3:29 PM
To: samba at lists.samba.org
Subject: Re: [Samba] Cannot Access Workgroup shares

Quoting Dan Grindstaff <dan at oakrun.net>:
> Hello All,
>
> I have set up samba server 3.0.33-0.fc8 and successfully created a share
> accessible by all machines in my workgroup.  When I open up network on my
> linux box I can see all other machines in the workgroup.  I have set up
> other shares on other machines and am able to see them but when I try to
> open the share from linux I get login message. I do not want to have to
log
> in from linux.  I have set up the shares on the windows machines to be
> accessible to everyone. TIA for any and all advice.
Well the Linux client behavior probably has little to do with the  
server side.  You might consider providing credentials in /etc/fstab  
and mount the shares that way.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba