From: Gabriel Barazer <gabriel@oxeva.fr>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [2.6.24.3][net] bug: TCP 3rd handshake abnormal timeouts
Date: Sun, 16 Mar 2008 17:24:38 +0100 [thread overview]
Message-ID: <47DD49C6.8040400@oxeva.fr> (raw)
In-Reply-To: <20080315085527.GA6239@1wt.eu>
Hi
On 03/15/2008 9:55:27 AM +0100, Willy Tarreau <w@1wt.eu> wrote:
> On Sat, Mar 15, 2008 at 09:47:24AM +0100, Gabriel Barazer wrote:
>
> Feel free to repost the whole issue overthere (along with your new tests)
> if you don't get useful replies in a few days.
>
>> By the way thanks for replying. It's hard to explain and describe a
>> problem when you know people will ask you hundreds of questions related
>> to application-level problems, or not reply because web/mysql problems
>> are so common and generally not related to any kernel issue.
>
> What caught my attention was the usual "3s delay", which is purely TCP
> and application-independant.
>
>
>>> Also, you say you have netfilter with conntrack. Is this on the client ?
>>> If so, you should try disabling it to rule out any possible bug in the
>>> connection tracking.
>> I have the conntrack on both the client and server, and unfortunately
>> can't disable it now on the client (I use it only for the REDIRECT
>> target on a precise destination address and port, not MySQL related),
>> however I will test today and disable it on the server, after I get some
>> sleep (although I think the issue is on the client).
>
> I'm sure it's a client issue too, that's why it would be reasonable to
> be able to try without conntrack. Can't you use a TCP proxy instead of
> REDIRECT ? Also, you said that you also noticed the same behaviour in
> other environments, maybe there you can disable conntrack ?
I was able to reproduce the bug multiple times without conntrack nor
netfilter on the client and the server(I recompiled the kernel disabling
the entire netfilter subsystem). The 3-second problem still occurs so we
can completely rule out contrack-related bugs.
What can we do and test next?
Gabriel
next prev parent reply other threads:[~2008-03-16 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47DB28E9.4050309@oxeva.fr>
[not found] ` <20080315065739.GL8953@1wt.eu>
2008-03-15 6:58 ` [2.6.24.3][net] bug: TCP 3rd handshake abnormal timeouts Willy Tarreau
2008-03-15 8:47 ` Gabriel Barazer
2008-03-15 8:55 ` Willy Tarreau
2008-03-16 16:24 ` Gabriel Barazer [this message]
2008-03-20 4:34 ` Willy Tarreau
2008-03-15 8:51 ` Gabriel Barazer
2008-03-15 15:27 ` Phil Oester
2008-03-15 8:53 Gabriel Barazer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47DD49C6.8040400@oxeva.fr \
--to=gabriel@oxeva.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).