From owner-freebsd-amd64@freebsd.org  Tue May 17 11:29:41 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
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 0E941B3E25C
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Tue, 17 May 2016 11:29:41 +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 F306D1842
 for <freebsd-amd64@FreeBSD.org>; Tue, 17 May 2016 11:29:40 +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 u4HBTebR031105
 for <freebsd-amd64@FreeBSD.org>; Tue, 17 May 2016 11:29:40 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: Tue, 17 May 2016 11:29:40 +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: shared+bugs.freebsd.org@twingly.com
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: <bug-209471-6-kbswjictMD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209471-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209471-6@https.bugs.freebsd.org/bugzilla/>
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: Tue, 17 May 2016 11:33:50 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 11:29:41 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209471

--- Comment #18 from Twingly <shared+bugs.freebsd.org@twingly.com> ---
(In reply to Robert Blayzor from comment #14)
> > One would think these two bug (or same one) would be a major regression=
 other people would run into. If not, why?

I do think other people are running into this. We do. It has happened to us
since early January, 5 times. In our cases it is mysqld that hangs. I think
this is related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D2047=
64.

Robert, can you check with procstat -t if your processes are in "vodead" st=
ate
when this happens?

Sorry for the quick post, I will try to post more information about our set=
up
later. Just some quicks notes: we have physical machines with FreeBSD 10.2,=
 we
use ZFS (mirrored SSDs).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=