Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 May 2016 11:29:40 +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-ZikL8lGQVC@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=209471

--- 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=204764.

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

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

-- 
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-ZikL8lGQVC>