From owner-freebsd-amd64@freebsd.org Mon May 16 21:47:48 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 922C9B38546 for ; Mon, 16 May 2016 21:47:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 82FE61316 for ; Mon, 16 May 2016 21:47:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4GLllpi006377 for ; Mon, 16 May 2016 21:47:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 209471] Listen queue overflow due to too many sockets stuck in CLOSED state Date: Mon, 16 May 2016 21:47:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 16 May 2016 22:26:58 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2016 21:47:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209471 --- Comment #14 from Robert Blayzor --- Will try tcpdrop the next time it happens. We normally can't catch it until= the health monitors pick it up as dead, thats' when we notice the kernel messag= es. Usually by that time a "kill -9" will not work on the process and the only = way to fix the problem is reboot. I'm still trying to figure out why we are affected by this issue and Bug 204426. Am I correct in that Bug 204426 is only VM memory related? If so, m= aybe I can jack up the physical memory to the VM and try turning VM off. AFAIK we're not doing anything special on the servers; just diskless boot V= M's, NFS root, a couple of memory disk filesystems (/etc and var, which do not g= row at all)... Just trying to figure out what in our environment is causing us = to see this A LOT. One would think these two bug (or same one) would be a major regression other people would run into. If not, why? --=20 You are receiving this mail because: You are on the CC list for the bug.=