From owner-freebsd-net@FreeBSD.ORG Mon Oct 10 06:31:07 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2073216A41F for ; Mon, 10 Oct 2005 06:31:07 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 93F8143D4C for ; Mon, 10 Oct 2005 06:31:06 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 54667 invoked from network); 10 Oct 2005 06:31:04 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 10 Oct 2005 06:31:04 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 10 Oct 2005 01:31:03 -0500 (CDT) From: Mike Silbersack To: Olivier Nicole In-Reply-To: <200510100622.j9A6MMbW014091@banyan.cs.ait.ac.th> Message-ID: <20051010012831.G60693@odysseus.silby.com> References: <200510100622.j9A6MMbW014091@banyan.cs.ait.ac.th> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: SYN limit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2005 06:31:07 -0000 On Mon, 10 Oct 2005, Olivier Nicole wrote: > For some reason, it seems that the MySQL server only accepts 50 > connections to the same resource comming from the same client at one > given time. 50 other connections are in SYN_SENT state. > > Any reason why this limit? FreeBSD has no SYN rate limit, but you could be running into TIME_WAIT recycling issues. Run a netstat on both the client and server, see if the port numbers match. For example, see if the client is trying to connect to port 3549 and the server has a TIME_WAIT socket on port 3549. The connection is supposed to recycle, but under certain conditions it might not... After doing that, try setting net.inet.ip.portrange.randomized=0 and see if the problem clears up at all. Mike "Silby" Silbersack