From owner-freebsd-stable@FreeBSD.ORG  Sun Jan 18 12:21:48 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 64286292
 for <freebsd-stable@freebsd.org>; Sun, 18 Jan 2015 12:21:48 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1FA2E352
 for <freebsd-stable@freebsd.org>; Sun, 18 Jan 2015 12:21:48 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1YCorS-000L6b-0k; Sun, 18 Jan 2015 13:21:46 +0100
Date: Sun, 18 Jan 2015 13:21:45 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Harald Schmalzbauer <h.schmalzbauer@omnilan.de>
Subject: Re: sonewconn: pcb 0x???: Listen queue overflow [Was: Re: lagg(8)
 causes ghost queue with igb(4)]
Message-ID: <20150118122145.GW44537@home.opsec.eu>
References: <54B962A3.9010308@omnilan.de>
 <54BBA2E3.5070401@omnilan.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54BBA2E3.5070401@omnilan.de>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jan 2015 12:21:48 -0000

Hi!

> I noticed another mysterium, at least for me. I'd highly appreciate if
> somebody could give me a hint how I can understand the following lines
> 
> sonewconn: pcb 0xfffff801b85907a8: Listen queue overflow: 151 already in
> queue awaiting acceptance (1 occurrences)

You have a socket open in the LISTEN state. Incoming connections
must be accept()'ed. If the process that LISTENs is too busy
to accept, the so-called 'listen-queue' is growing.

I have found

kern.ipc.soacceptqueue: 128

and I assume that this is the max. number of incoming connections waiting
for accept before the next incoming connection will cause that error
(and is not successful any more).

I do not know how to match the pcb (protocol control block) back
to the process/LISTEN in question, but maybe someone else knows this ?

-- 
pi@opsec.eu            +49 171 3101372                         5 years to go !