From owner-freebsd-bugs@FreeBSD.ORG  Mon Sep  8 06:25:38 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4A528DB6
 for <freebsd-bugs@FreeBSD.org>; Mon,  8 Sep 2014 06:25:38 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 31AE71BE0
 for <freebsd-bugs@FreeBSD.org>; Mon,  8 Sep 2014 06:25:38 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s886PcH7017860
 for <freebsd-bugs@FreeBSD.org>; Mon, 8 Sep 2014 06:25:38 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192889] accept4 socket hangs in CLOSED (memcached)
Date: Mon, 08 Sep 2014 06:25:38 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: arne.claus@trivago.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192889-8-UOY3ElazJF@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192889-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192889-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 06:25:38 -0000

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

--- Comment #7 from Arne Claus <arne.claus@trivago.com> ---
FreeBSD 9.2-RELEASE-p1 #0 r258345
memcached 1.4.17
libevent 1.4.14b
--- No Problems

FreeBSD 9.2-RELEASE-p1 #0 r258345
memcached 1.4.20
libevent 1.4.14b
--- Stuck

FreeBSD 9.2-RELEASE-p1 #0 r258345
memcached 1.4.20
libevent 2.0.21
--- No Problems

FreeBSD 10.0-STABLE #0 r269376
memcached 1.4.20
libevent 2.0.21
--- Stuck

For more test results and remarks see the memcached issue
https://code.google.com/p/memcached/issues/detail?id=375

It is already quite clear that the problem is not bound to the operating
system's limits as we can reproduce the problem with smaller settings, too.

-- 
You are receiving this mail because:
You are the assignee for the bug.