Date: Sun, 18 Jan 2015 13:24:57 +0100 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: Kurt Jaeger <lists@opsec.eu> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: sonewconn: pcb 0x???: Listen queue overflow [Was: Re: lagg(8) causes ghost queue with igb(4)] Message-ID: <54BBA619.5030702@omnilan.de> In-Reply-To: <20150118122145.GW44537@home.opsec.eu> References: <54B962A3.9010308@omnilan.de> <54BBA2E3.5070401@omnilan.de> <20150118122145.GW44537@home.opsec.eu>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Bezüglich Kurt Jaeger's Nachricht vom 18.01.2015 13:21 (localtime): > 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 ? Thanks for your help!!! I guess after the socket was closed, it's not possible anymore. 'netstat -An' and greping will do it while active I guess. Thanks, -Harry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlS7phkACgkQLDqVQ9VXb8jI1ACgtBsrbmvBfjrIsMCQFQzhdZyn bUgAoMjGHN9qtKfJstJ6avhgP1jjfUK4 =slcX -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54BBA619.5030702>