kern/147756: [libc] open_socket_in: Protocol not supported -
after a few days?
Kirill A Sarksyan
dot at kkursor.ru
Mon Aug 9 21:40:04 UTC 2010
The following reply was made to PR kern/147756; it has been noted by GNATS.
From: Kirill A Sarksyan <dot at kkursor.ru>
To: Martin Minkus <martin.minkus at pulseutilities.co.nz>
Cc: bug-followup <bug-followup at FreeBSD.org>
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 at kkursor.ru]
> Sent: Tuesday, 10 August 2010 00:35
> To: bug-followup at 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY LINK="#0000ff">
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.<BR>
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.<BR>
<BR>
В Втр, 10/08/2010 в 09:23 +1200, Martin Minkus пишет:
<BLOCKQUOTE TYPE=CITE>
In my case it was bad hardware. Seemed to be the PCI bus, so probably the southbridge.<BR>
<BR>
<BR>
<BR>
Anything using PCIe was completely unaffected, and mem tests running for days passed fine.<BR>
<BR>
<BR>
<BR>
Traffic going over the pci bus, even the onboard nic would silently get corrupted.<BR>
<BR>
<BR>
<BR>
Moved the hardware onto a new motherboard and all the issues magically disappeared.....<BR>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<B>From:</B> Kirill A Sarksyan [mailto:dot at kkursor.ru] <BR>
<B>Sent:</B> Tuesday, 10 August 2010 00:35<BR>
<B>To:</B> bug-followup at FreeBSD.org; Martin Minkus<BR>
<B>Subject:</B> Re: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul 1 01:27:47 MSD 2010.<BR>
On start Samba log contains:<BR>
[2010/08/09 16:19:04, 1] smbd/files.c:177(file_init)<BR>
file_init: Information only: requested 16384 open files, 7014 are available.<BR>
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)<BR>
open_socket_in(): socket() call failed: Protocol not supported<BR>
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)<BR>
smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
[2010/08/09 16:19:04, 0] lib/util_sock.c:902(open_socket_in)<BR>
open_socket_in(): socket() call failed: Protocol not supported<BR>
[2010/08/09 16:19:04, 0] smbd/server.c:457(smbd_open_one_socket)<BR>
smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
<BR>
%pkg_info | grep samba<BR>
samba34-3.4.8 A free SMB and CIFS client and server for UNIX<BR>
<BR>
And Windows clients cannot use Samba shares at all.<BR>
<BR>
<BR>
<BR>
<BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>
--=-Gm/lsWSUG+RZpBXZBoJ4--
More information about the freebsd-bugs
mailing list