Samba is very noicy in the logs. My server's /var/log/messages is now 62 MB large and it's 99% full with this error: Oct 16 23:47:37 snigel smbd[29700]: read_socket_data: recv failure for 4. Error = F
Samba is very noicy in the logs. My server's /var/log/messages is now 62 MB large and it's 99% full with this error: Oct 16 23:47:37 snigel smbd[29700]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:47:39 snigel smbd[29699]: [2004/10/16 23:47:39, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:47:39 snigel smbd[29699]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:48:05 snigel smbd[29705]: [2004/10/16 23:48:05, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:48:05 snigel smbd[29705]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:48:10 snigel smbd[29707]: [2004/10/16 23:48:10, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:48:10 snigel smbd[29707]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:48:10 snigel smbd[29710]: [2004/10/16 23:48:10, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:48:10 snigel smbd[29710]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:48:15 snigel smbd[29714]: [2004/10/16 23:48:15, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:48:15 snigel smbd[29714]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:48:15 snigel smbd[29716]: [2004/10/16 23:48:15, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:48:15 snigel smbd[29716]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern Oct 16 23:48:24 snigel smbd[29720]: [2004/10/16 23:48:24, 0] lib/util_sock.c:read_socket_data(384) Oct 16 23:48:24 snigel smbd[29720]: read_socket_data: recv failure for 4. Error = Förbindelse borttagen av partnern "Förbindelse borttagen av partnern" = Connection reset by peer Samba 3.0.7-r1 is installed but I have had this problem with other versions too. I have tried downgrading and upgrading samba, building it with more conservative CFLAGS, building it without stack-protector and tweaking the smb.conf file in different ways but nothing has helped. I have also searched google for this and found several others with the same or similar problem but no solution yet. :( snigel log # emerge info Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8-gentoo-r7) ================================================================= System uname: 2.6.8-gentoo-r7 i686 Pentium II (Deschutes) Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium2 -pipe -fomit-frame-pointer -ffast-math -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium2 -pipe -fomit-frame-pointer -ffast-math -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="aalib acpi alsa apache2 apm avi berkdb bitmap-fonts crypt encode f77 fbcon foomaticdb gdbm gif gpm imlib libg++ libwww linguas_sv mad mikmod mmx mysql ncurses nls nptl objc offensive oggvorbis pam pdflib perl pic pnp python readline samba sdl slang ssl svga tcpd usb x86 xprint zlib" Reproducible: Always Steps to Reproduce:
Created attachment 41989 [details] smb.conf smb.conf
question: can you try with 'use sendfile = No' in global section? this seems like a sort of protocol mismatch between server and client
It didn't help! I forgot to say that samba works completly except for this. I have no problem accesing files from windows computers. My server has two network interfaces. One connected to the internet (eth0) and one connected to the network (eth1). I think I've managed to get samba running on only eth1. I'm going to try to disconnect both tonight when no one is using the server and see if it helps.
When eth0 is disconnected there is a lot less errors. Maybe samba is not limited to run on only eth1 after all? But I wold like to get rid of these errors compleatly if it's possible since they are pointless.
Maybe inteface kernel module: what's your network card info? (lspci, modinfo, whatever pertinent). BTW: with newer kernels?
snigel root # lsmod Module Size Used by 3c59x 23016 0 8139too 11296 0 crc32 2944 1 8139too sr_mod 9252 0 scsi_mod 44384 1 sr_mod snigel root # lspci 0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) 0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) 0000:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) 0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) 0000:00:0b.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 Audiodrive (rev 01) 0000:00:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30) 0000:00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP (rev 3a) The 3com card is eth1 connected to the network and the realtek is eth0 connected to the internet. The kernel is 2.6.9-ck3. I have been running different versions of gentoo-dev-sources and ck-sources 2.6.8 previously but I don't think that changed anything. I was able to reduce the errors a lot by adding: bind interfaces only = yes to the config-file so this is'nt mych of a problem anymore. Thanks anyway!
It has been running for some time now and the messages log is no longer flooded with samba errors. The fix was to add: bind interfaces only = yes to smb.conf. So this bug can probably be closed now!
All right: kernel interface stuff, so closing now.
