From owner-freebsd-amd64@freebsd.org Mon May 16 22:19:28 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 6AD8CB38E11 for ; Mon, 16 May 2016 22:19:28 +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 431B216E5 for ; Mon, 16 May 2016 22:19:28 +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 u4GMJSFh005148 for ; Mon, 16 May 2016 22:19:28 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 22:19:28 +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 22:19:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209471 --- Comment #15 from Robert Blayzor --- I believe I have stumbled onto this problem in it's early stages. I notice = this by catching a process that seems to have a connection in a "CLOSED" state f= or what seems like forever. If I look at it closer... dev@mta2 [~] netstat -an | grep CLOSED tcp6 0 0 2607:f058:110:2:.25 2607:f058:110:2:.40858 CLOSED dev@mta2 [~] sockstat | grep 40858 mailnull exim 35876 7 tcp6 2607:f058:110:2::1:2:25 2607:f058:110:2::f:0:40858 mailnull exim 35876 9 tcp6 2607:f058:110:2::1:2:25 2607:f058:110:2::f:0:40858 dev@mta2 [~] sudo tcpdrop 2607:f058:110:2::1:2 25 2607:f058:110:2::f:0 40858 tcpdrop: 2607:f058:110:2::1:2 25 2607:f058:110:2::f:0 40858: No such process If I kill the process and restart it... the old process sticks around and t= he socket never clears. dev@mta2 [~] sudo killall -9 exim dev@mta2 [~] ps auxww | grep exim mailnull 35876 0.0 0.4 41708 8184 - DL 9:21PM 0:09.40 /usr/local/sbin/exim -bd -q10m dev@mta2 [~] netstat -an | grep CLOSED tcp6 0 0 2607:f058:110:2:.25 2607:f058:110:2:.40858 CLOSED dev@mta2 [~] sudo service exim start Starting exim. dev@mta2 [~] gps exim root 39120 0.2 0.4 41708 8364 - Ss 10:15PM 0:00.00 /usr/local/sbin/exim -bd -q10m mailnull 35876 0.0 0.4 41708 8184 - DL 9:21PM 0:09.48 /usr/local/sbin/exim -bd -q10m sockstat | grep 40858 mailnull exim 35876 7 tcp6 2607:f058:110:2::1:2:25 2607:f058:110:2::f:0:40858 mailnull exim 35876 9 tcp6 2607:f058:110:2::1:2:25 2607:f058:110:2::f:0:40858 I'm not expert on kernel VM, but think stinks as related to previous bug.=20 Top state shows: vmf_de ? 35876 mailnull 1 20 0 41708K 8184K vmf_de 2 0:10 0.00% exim --=20 You are receiving this mail because: You are on the CC list for the bug.=