From owner-freebsd-bugs@FreeBSD.ORG Mon Aug 9 21:40:04 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E49EB1065692 for ; Mon, 9 Aug 2010 21:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D2C838FC1C for ; Mon, 9 Aug 2010 21:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o79Le3nn072841 for ; Mon, 9 Aug 2010 21:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o79Le3SX072840; Mon, 9 Aug 2010 21:40:03 GMT (envelope-from gnats) Date: Mon, 9 Aug 2010 21:40:03 GMT Message-Id: <201008092140.o79Le3SX072840@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kirill A Sarksyan Cc: Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days? X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kirill A Sarksyan List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2010 21:40:04 -0000 The following reply was made to PR kern/147756; it has been noted by GNATS. From: Kirill A Sarksyan To: Martin Minkus Cc: bug-followup Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days? Date: Tue, 10 Aug 2010 01:31:56 +0400 --=-Gm/lsWSUG+RZpBXZBoJ4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Strange. The computer I speak about works as my home server (including WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4. I found a strange thing - Samba correctly works from inside of home network, but fails to work from the Internet. I will re-read configuration how-to, maybe there is some differencies between old Samba and the new one, because of which new Samba does not listen globally available network interfaces. В Втр, 10/08/2010 в 09:23 +1200, Martin Minkus пишет: > In my case it was bad hardware. Seemed to be the PCI bus, so probably > the southbridge. > > > > Anything using PCIe was completely unaffected, and mem tests running > for days passed fine. > > > > Traffic going over the pci bus, even the onboard nic would silently > get corrupted. > > > > Moved the hardware onto a new motherboard and all the issues magically > disappeared..... > > > > > From: Kirill A Sarksyan [mailto:dot@kkursor.ru] > Sent: Tuesday, 10 August 2010 00:35 > To: bug-followup@FreeBSD.org; Martin Minkus > Subject: Re: kern/147756: [libc] open_socket_in: Protocol not > supported - after a few days? > > > > > > I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul 1 01:27:47 MSD > 2010. > On start Samba log contains: > [2010/08/09 16:19:04, 1] smbd/files.c:177(file_init) > file_init: Information only: requested 16384 open files, 7014 are > available. > [2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in) > open_socket_in(): socket() call failed: Protocol not supported > [2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket) > smbd_open_once_socket: open_socket_in: Protocol not supported > [2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in) > open_socket_in(): socket() call failed: Protocol not supported > [2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket) > smbd_open_once_socket: open_socket_in: Protocol not supported > > %pkg_info | grep samba > samba34-3.4.8 A free SMB and CIFS client and server for UNIX > > And Windows clients cannot use Samba shares at all. > > > > --=-Gm/lsWSUG+RZpBXZBoJ4 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit Strange. The computer I speak about works as my home server (including WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.
I found a strange thing - Samba correctly works from inside of home network, but fails to work from the Internet. I will re-read configuration how-to, maybe there is some differencies between old Samba and the new one, because of which new Samba does not listen globally available network interfaces.

В Втр, 10/08/2010 в 09:23 +1200, Martin Minkus пишет:
In my case it was bad hardware. Seemed to be the PCI bus, so probably the southbridge.

 

Anything using PCIe was completely unaffected, and mem tests running for days passed fine.

 

Traffic going over the pci bus, even the onboard nic would silently get corrupted.

 

Moved the hardware onto a new motherboard and all the issues magically disappeared.....

 

From: Kirill A Sarksyan [mailto:dot@kkursor.ru]
Sent: Tuesday, 10 August 2010 00:35
To: bug-followup@FreeBSD.org; Martin Minkus
Subject: Re: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?


 

I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul  1 01:27:47 MSD 2010.
On start Samba log contains:
[2010/08/09 16:19:04,  1] smbd/files.c:177(file_init)
  file_init: Information only: requested 16384 open files, 7014 are available.
[2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
  open_socket_in(): socket() call failed: Protocol not supported
[2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Protocol not supported
[2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
  open_socket_in(): socket() call failed: Protocol not supported
[2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Protocol not supported

%pkg_info | grep samba
samba34-3.4.8       A free SMB and CIFS client and server for UNIX

And Windows clients cannot use Samba shares at all.





--=-Gm/lsWSUG+RZpBXZBoJ4--