Date: Mon, 16 May 2016 19:25:24 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 209471] Listen queue overflow due to too many sockets stuck in CLOSED state Message-ID: <bug-209471-2472-wUKaJFaio3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209471-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-209471-2472@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=3D209471 --- Comment #6 from Robert Blayzor <rblayzor@inoc.net> --- I do not have an environment that would allow me really to test it. This problem does seem a lot more apparently after upgrading to 10.3 however. It= 's either that, or the work around for BugID 204426 unmasked this one from happening. Bug 204426 we would see our processes normally die, so they never really ran for longer period of time before we had to restart them. We added the patch for PR 204426, and processes seem stable now, but now we have this bug. I believe we used to see this in in 10.2 as well, but not ne= arly as often now that we seem to have 204426 fixed. The application doesn't seem to matter. Our environment has not changed. The only real special setup we have is also described in 204426. ESXi hyperviso= r, VMX NIC driver, and NFS mounted root FS. Other than the sysctl knobs previo= usly mentioned, nothing else special other than a non-GENERIC kernel; but all we= did was remove modules and drivers we do not use so kernel build time is faster. One thing I did not check is to see if this is a V6 socket only issue or if= V4 is also affected. I can still SSH into the server when this happens, only t= he process with the full queue and lots of sockets stuck in CLOSED seems to h= ung. 9 times out of 10 only a server reboot clears the issue. Rarely we can mana= ge to kill -9 the process and restart it. --=20 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-209471-2472-wUKaJFaio3>