...@1wt.eu]
Sent: Wednesday, October 14, 2009 12:38 PM
To: Jonah Horowitz
Cc: Hank A. Paulson; haproxy@formilux.org
Subject: Re: Problems with long connect times
Hi Jonah,
On Wed, Oct 14, 2009 at 12:31:07AM -0700, Jonah Horowitz wrote:
driver: tg3
version: 3.98
firmware-version: 5721-v3.55a
bus-info
> -Original Message-
> From: Willy Tarreau [mailto:w...@1wt.eu]
> Sent: Wednesday, October 14, 2009 12:38 PM
> To: Jonah Horowitz
> Cc: Hank A. Paulson; haproxy@formilux.org
> Subject: Re: Problems with long connect times
>
> Hi Jonah,
>
> On Wed, Oc
> The only way to detect this is to put a sniffer on both ends and
> compare sequence numbers. They must match. If not, you have such a
> nasty thing in the middle that needs to be fixed (for PIX and FWSM,
> there is an option I don't remember for that).
The option is called norandomseq. It can be
Hi Jonah,
On Wed, Oct 14, 2009 at 12:31:07AM -0700, Jonah Horowitz wrote:
>
> driver: tg3
> version: 3.98
> firmware-version: 5721-v3.55a
> bus-info: :03:00.0
OK this is fine.
> Not running bnx2. Looks like it's not a 65563 limit either, I've been
> graphing it and it's up to 80k sometimes
driver: tg3
version: 3.98
firmware-version: 5721-v3.55a
bus-info: :03:00.0
Not running bnx2. Looks like it's not a 65563 limit either, I've been
graphing it and it's up to 80k sometimes, but it goes up and down.
When it fails, it seems like it's either 3 seconds or 9 seconds. Would tcp
ret
On Tue, Oct 13, 2009 at 12:52:55PM -0700, Jonah Horowitz wrote:
> netstat -ant | grep tcp | tr -s ' ' ' ' | awk '{print $6}' | sort | uniq
> -c
>193 CLOSE_WAIT
>316 CLOSING
>215 ESTABLISHED
>252 FIN_WAIT1
> 4 FIN_WAIT2
> 1 LAST_ACK
> 10 LISTEN
>237 SYN_RECV
> 6138
tting a 65536 connection
limit.
> -Original Message-
> From: Hank A. Paulson [mailto:h...@spamproof.nospammail.net]
> Sent: Monday, October 12, 2009 9:14 PM
> To: haproxy@formilux.org
> Subject: Re: Problems with long connect times
>
> A couple of guesses you might loo
A couple of guesses you might look at -
I have found the stats page to show deceptively low numbers at times.
You might want to check the http log stats that show the
global/frontend/backend queue numbers around the time those requests. My guess
is that the cases where you are seeing 3 second ti
8 matches
Mail list logo