Bug 2096 - getpeername failed while streaming
Summary: getpeername failed while streaming
Status: RESOLVED WONTFIX
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: smbmount (unmaintained) (show other bugs)
Version: 3.0.9
Hardware: All Windows XP
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-28 12:37 UTC by Luca Mottola
Modified: 2005-02-17 09:16 UTC (History)
1 user (show)

See Also:


Attachments
DEBUG 4 of my server (14.64 KB, application/octet-stream)
2004-12-02 13:01 UTC, Matthew A. R. Sherian
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Mottola 2004-11-28 12:37:04 UTC
If I'm listening to MP3 music files from a Samba share on a WinXP Prof SP2
client and at the same time I try to browse images stored on the same server
with the "preview" mode, then smbd hangs and the music suddenly stops. In
particular, my MP3 player reports that the file is "no longer available".
My Samba server is configured with two NICs as a PDC. 
This is my smb.conf file:

#======================= Global Settings =====================================
[global]

	netbios name = NOEL
	workgroup = MOTTOLA

	os level = 33
	preferred master = yes
	domain master = yes
 	local master = yes

	;hosts allow = 192.168.0.0/24 127.0.0.1

	log file = /usr/local/samba/var/log.%m
	log level = 1
	max log size = 50

	security = user
	encrypt passwords = yes
	smb passwd file = /etc/smbpasswd

	interfaces = 192.168.0.0/24
	socket address = 192.168.0.1

	wins support = yes
	wins proxy = yes
	dns proxy = no

	domain logons = yes
	
	logon home = \\%L\UserData\%U
	logon drive = Z:

	printing = cups
	printcap name = cups

[EpsonEPL5900Raw]

	path = /var/spool/samba
	printable = yes
	browseable = yes
	printing = cups
	printer = EpsonEPL5900Raw
	public = no
	printer admin = root @users
	writable = yes
	use client driver = yes
	guest ok = no

#============================ Share Definitions ==============================

# Un-comment the following and create the netlogon directory for Domain Logons
[netlogon]
    	comment = Network Logon Service
    	path = /usr/local/samba/netlogon
    	guest ok = yes
    	writable = no
	browsable = no
    	share modes = no

[UserData]
    	path = /userdata
	writable = yes
	browsable = yes
	map archive = yes
	valid users = @users root
	oplocks = false
	level2 oplocks = false

[UserSpace]
    	path = /userspace
	writable = yes
	browsable = yes
	map archive = yes
	create mask = 775
	directory mask = 775
	force user = root
	force group = users
	valid users = @users root
	oplocks = false
	level2 oplocks = false

The options related to oplocks have been included for trying to solve the
problem, but it did not work.
The only error my log files report (several times) is the following:

[2004/11/27 12:41:16, 0] lib/util_sock.c:get_peer_addr(978)
  getpeername failed. Error was Transport endpoint is not connected
Comment 1 Matthew A. R. Sherian 2004-12-02 12:58:51 UTC
This bug also exists in a SMB 3.09 <-> 3.09 environment.

On the server side: 
[2004/11/29 14:06:30, 0] lib/util_sock.c:get_peer_addr(978)
  getpeername failed. Error was Transport endpoint is not connected


On the client:

Dec  2 14:01:09 linux-mars kernel: smb_add_request: request [277f6b80, mid=814]
timed out!
Dec  2 14:01:09 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:01:39 linux-mars kernel: smb_add_request: request [277f6b80, mid=829]
timed out!
Dec  2 14:01:39 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:02:09 linux-mars kernel: smb_add_request: request [277f6b80, mid=839]
timed out!
Dec  2 14:02:09 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:02:39 linux-mars kernel: smb_add_request: request [277f6b80, mid=849]
timed out!
Dec  2 14:02:39 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:03:09 linux-mars kernel: smb_add_request: request [277f6b80, mid=857]
timed out!
Dec  2 14:03:09 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:03:39 linux-mars kernel: smb_add_request: request [277f6b80, mid=870]
timed out!
Dec  2 14:03:39 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:04:09 linux-mars kernel: smb_add_request: request [277f6b80, mid=878]
timed out!
Dec  2 14:04:09 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:04:39 linux-mars kernel: smb_add_request: request [277f6b80, mid=886]
timed out!
Dec  2 14:04:39 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:05:09 linux-mars kernel: smb_add_request: request [277f6b80, mid=910]
timed out!
Dec  2 14:05:09 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0
Dec  2 14:05:39 linux-mars kernel: smb_add_request: request [277f6b80, mid=919]
timed out!
Dec  2 14:05:39 linux-mars kernel: smb_trans2: invalid data, disp=0, cnt=0,
tot=0, ofs=0


Dec  2 14:54:04 linux-mars mount.smbfs[5479]: [2004/12/02 14:54:04, 0]
tdb/tdbutil.c:tdb_log(725)
Dec  2 14:54:04 linux-mars mount.smbfs[5479]:  
tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 19 ltype=0 (Bad file
descriptor)
Dec  2 14:54:04 linux-mars mount.smbfs[5479]: [2004/12/02 14:54:04, 0]
tdb/tdbutil.c:tdb_log(725)
Dec  2 14:54:04 linux-mars mount.smbfs[5479]:  
tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 19 ltype=1 (Bad file
descriptor)
Dec  2 14:54:04 linux-mars mount.smbfs[5479]: [2004/12/02 14:54:04, 0]
tdb/tdbutil.c:tdb_log(725)
Dec  2 14:54:04 linux-mars mount.smbfs[5479]:  
tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 19 ltype=1 (Bad file
descriptor)
Dec  2 14:54:04 linux-mars kernel: SMB connection re-established (-5)

Comment 2 Matthew A. R. Sherian 2004-12-02 13:01:04 UTC
Created attachment 821 [details]
DEBUG 4 of my server
Comment 3 Luca Mottola 2005-01-12 11:37:48 UTC
I'm using a stock Linux kernel 2.4.24 and the latest Samba release (3.0.10),
that still does not fix the problem... 
Comment 4 Filipus Klutiero 2005-01-14 14:38:04 UTC
Note that Matthew reports his clients getting timeouts are running kernel
2.6.9_*_FC3 series builds.
Comment 5 Gerald (Jerry) Carter (dead mail address) 2005-02-17 09:16:12 UTC
we don't actually support smbfs.  You'll have to talk to 
the kernel maintainers about that.  You might want to test
the cifs fs in the 2.6. linux kernel.  See 
http://www.samba.org/samba.download/