Date: Wed, 28 May 2008 23:07:08 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Robert Blayzor <rblayzor.bulk@inoc.net> Cc: freebsd-stable@freebsd.org Subject: Re: Sockets stuck in FIN_WAIT_1 Message-ID: <20080529060708.GA66432@eos.sc1.parodius.com> In-Reply-To: <B42F9BDF-1E00-45FF-BD88-5A07B5B553DC@inoc.net> References: <B42F9BDF-1E00-45FF-BD88-5A07B5B553DC@inoc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 28, 2008 at 06:13:04PM -0400, Robert Blayzor wrote: > Here is what I have on the server now: > > and loader.conf > > accf_http_load="YES" You shouldn't bother with this. Let the apache22 rc.d script handle loading it dynamically. Use apache22_http_accept_enable="yes" in rc.conf. I've read reports in the past how the accept filter can cause FIN_WAIT issues, but I can't remember if that's FIN_WAIT_2 or FIN_WAIT_1. I've also read that pf(4) could possibly cause what you're seeing, so if you have broken firewall rules, those may be responsible for this behaviour. Finally, for what it's worth, we don't have this problem on RELENG_6 or RELENG_7 using Apache 2.2 with the accept filter, and also use pf(4). We use absolutely no tuning in sysctl.conf for any of the things you have listed. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080529060708.GA66432>