From owner-freebsd-stable@FreeBSD.ORG  Thu Jun  3 13:36:39 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C021716A4CE
	for <freebsd-stable@freebsd.org>;
	Thu,  3 Jun 2004 13:36:39 -0700 (PDT)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1B28A43D48
	for <freebsd-stable@freebsd.org>;
	Thu,  3 Jun 2004 13:36:39 -0700 (PDT)	(envelope-from silby@silby.com)
Received: (qmail 70361 invoked from network); 3 Jun 2004 20:36:37 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 3 Jun 2004 20:36:37 -0000
X-pair-Authenticated: 209.68.2.70
Date: Thu, 3 Jun 2004 15:36:36 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Pete French <petefrench@keithprowse.com>
In-Reply-To: <E1BVpnO-00009A-Ai@dilbert.firstcallgroup.co.uk>
Message-ID: <20040603153507.A23800@odysseus.silby.com>
References: <E1BVpnO-00009A-Ai@dilbert.firstcallgroup.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: jaco@premsoft.co.za
cc: freebsd-stable@freebsd.org
Subject: Re: Possible portrange.randomized problems?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2004 20:36:39 -0000


On Thu, 3 Jun 2004, Pete French wrote:

> > Sounds like we're confusing problems then.  I have no insight into the
> > MySQL problems, unfortunately.
>
> The mysql problem is (for me) also the portrange problem. See other email,
> the mysql connection problem goes away when I disable the randomisation. As
> it only started with 4.10 (when randomisation arived) then thats fairly
> good circumstantial evidence. Other people seeem to have been having
> other problems with mysql since 4.9 though.
>
> -pcf.

Are you using TCP sockets for the connection to MySQL?

If the MySQL connections are triggered by some sort of website, perhaps
you could use http_load or apachebench to cause the problem to happen
quickly, thereby allowing you to test with portrange=1 and confirm whether
or not sockets are (temporarily) stick in the SYN_SENT state.

Mike "Silby" Silbersack