Date: Thu, 15 Jan 2015 13:47:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 192889] accept4 socket hangs in CLOSED (memcached) Message-ID: <bug-192889-8-FcUZu8lD2r@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192889 --- Comment #14 from Arne Claus <arne.claus@trivago.com> --- We tested memcached 1.4.20 again on FreeBSD 10.1 and this version does not show any hangs, too. So at the moment it looks like something on the FreeBSD side caused the issue. It would be great if someone with a little more knowledge on the network topic could post an overview on what changed in the network stack / accept chain for FreeBSD 10.1 so we can pin down the problem a little bit more. The current state is a little bit uncomfortable as memcached now seems to run stable but nobody knows why. The FreeBSD changelog only lists some security issue in the TCP/IP stack but those do not seem very related (I did not see the code though). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192889-8-FcUZu8lD2r>