From: Eric Dumazet <dada1@cosmosbay.com>
To: James Nichols <jamesnichols3@gmail.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
linux-kernel@vger.kernel.org,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: After many hours all outbound connections get stuck in SYN_SENT
Date: Wed, 19 Dec 2007 19:03:27 +0100 [thread overview]
Message-ID: <47695CEF.4090908@cosmosbay.com> (raw)
In-Reply-To: <83a51e120712190943m3bf0e2e4v2ea6b660142e9a5a@mail.gmail.com>
James Nichols a écrit :
> On 12/19/07, Eric Dumazet <dada1@cosmosbay.com> wrote:
>> James Nichols a écrit :
>>>> So you see outgoing SYN packets, but no SYN replies coming from the remote
>>>> peer ? (you mention ACKS, but the first packet received from the remote
>>>> peer should be a SYN+ACK),
>>> Right, I meant to say SYN+ACK. I don't see them coming back.
>> So... Really unlikely a linux problem, but ...
>>
>
>
> I don't know how you can be so sure. Turning tcp_sack off instantly
> resovles the problem and all connections are succesful. I can't
> imagine even the most far-fetched scenario where a router or every
> single remote endpoints would suddenly stop causing the problem just
> by removing a single TCP option.
>
>
>>> I can take these captures and take a look at the results.
>>> Unfortunately, I don't think I'll be able to make the captures
>>> available to the general public.
>> I dont understand, why dont you change IPs to mask them with 192.168.X.Y, or
>> just ME, and peer1, peer2, peer...
>
> I will see if I can do that, but it's major pain with 2000 hosts.
> Plus, there is application data in the packets that I can't allow into
> the public domain. I really don't think I can pull it off... I
> literally would have to go through our legal department.
I still dont understand.
"tcpdump -p -n -s 1600 -c 10000" doesnt reveal User data at all.
Without any exact data from you, I am afraid nobody can help.
>
>> Random ideas :
>>
>> 1) Is your server behind a NET router or something ?
>
> What's a NET router? I am behind a Cisco router and a firewall, but
> these network components have completely been replaced/rebuilt several
> times in the 4+ years that we've had this problem. I've looked at the
> logs there and neither are doing anything other than passing the
> traffic along.
Typo error, I meant NAT. Most routers doing NAT have some limits, timers, hacks...
>
>> 2) Are you sure you are not using connection tracking, and hit a limit on it ?
>
> I'm using ip_conntrack, but the limit I have for max entries is 65K.
> The most I've seen in there are a couple thousand- that was one of the
> first things I monitored very closely.
Now please try without conn tracking module. I saw many failures in the past
that were trigered by conntrack.
Do you have some firewall rules, using some netfilter modules like hashlimit ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-12-19 18:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83a51e120712141239u52d2dd68p1b6ee7ed08f2cecf@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0712180009390.32270@fbirervta.pbzchgretzou.qr>
[not found] ` <83a51e120712180734i334399dbl51f44fe32d815f7d@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0712181704380.4422@fbirervta.pbzchgretzou.qr>
[not found] ` <83a51e120712180845k6cadf67bn5dd66fb2d3ac72d4@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0712181818360.4422@fbirervta.pbzchgretzou.qr>
[not found] ` <83a51e120712181009pf954f43mcb63ea4dab638458@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0712181910580.4422@fbirervta.pbzchgretzou.qr>
[not found] ` <83a51e120712181021p4c4c2a13g8820271f1e00361b@mail.gmail.com>
[not found] ` <4768123A.7040603@cosmosbay.com>
[not found] ` <83a51e120712181144l65633b32r72cc369f9d012f47@mail.gmail.com>
2007-12-18 20:37 ` After many hours all outbound connections get stuck in SYN_SENT Eric Dumazet
2007-12-18 21:20 ` Jan Engelhardt
2007-12-19 16:53 ` James Nichols
2007-12-19 17:07 ` Eric Dumazet
2007-12-19 17:43 ` James Nichols
2007-12-19 17:58 ` Jan Engelhardt
2007-12-19 18:12 ` James Nichols
2007-12-20 14:41 ` Glen Turner
2007-12-20 16:37 ` James Nichols
2007-12-20 21:05 ` Ilpo Järvinen
2007-12-21 6:06 ` Jan Engelhardt
2007-12-21 4:51 ` Glen Turner
2007-12-21 13:57 ` James Nichols
2007-12-19 18:03 ` Eric Dumazet [this message]
2007-12-19 21:27 ` Ilpo Järvinen
2007-12-20 16:08 ` James Nichols
2007-12-20 20:44 ` Ilpo Järvinen
2007-12-20 20:49 ` Justin Banks
2007-12-16 16:34 James Nichols
2007-12-17 16:27 ` James Nichols
2007-12-19 12:54 ` Ilpo Järvinen
2007-12-19 17:38 ` James Nichols
2007-12-19 18:32 ` Ilpo Järvinen
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=47695CEF.4090908@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=jamesnichols3@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).