All of lore.kernel.org
 help / color / mirror / Atom feed
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 18:07:24 +0100	[thread overview]
Message-ID: <47694FCC.1020507@cosmosbay.com> (raw)
In-Reply-To: <83a51e120712190853q33d9c7c1t4a46380665b7538b@mail.gmail.com>

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 ...

> 
> 
>> When the problem comes, instead of restarting the application, please take a
>> tcpdump of say 10.000 packets.
>> Then turn off tcp_sack and take a 2nd tcpdump sample, and make both samples
>> available to us.
> 
> 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...

> 
> 
> 
>> If turning off tcp_sack makes the problem go away, why dont you turn it off
>> all the time ?
> 
> Unfortunately, I think that will be the answer if I can't get any help
> fixing this problem in the kernel.  It's a bummer, because many of the
> remote hosts my application communicates with are on wireless links,
> so there may be performance implications to turning SACK off.
> 

Random ideas :

1) Is your server behind a NET router or something ?
2) Are you sure you are not using connection tracking, and hit a limit on it ?



  reply	other threads:[~2007-12-19 17:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14 20:39 After many hours all outbound connections get stuck in SYN_SENT James Nichols
2007-12-17 23:14 ` Jan Engelhardt
2007-12-18 15:34   ` James Nichols
2007-12-18 16:05     ` Jan Engelhardt
2007-12-18 16:45       ` James Nichols
2007-12-18 17:19         ` Jan Engelhardt
2007-12-18 18:09           ` James Nichols
2007-12-18 18:14             ` Jan Engelhardt
2007-12-18 18:21               ` James Nichols
2007-12-18 18:30                 ` Jan Engelhardt
2007-12-18 18:32                 ` Eric Dumazet
2007-12-18 19:44                   ` James Nichols
2007-12-18 20:37                     ` Eric Dumazet
2007-12-18 21:20                       ` Jan Engelhardt
2007-12-19 16:53                       ` James Nichols
2007-12-19 17:07                         ` Eric Dumazet [this message]
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
2007-12-19 18:03                               ` Eric Dumazet
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-18 19:45                   ` James Nichols
2007-12-18 20:28                     ` Chuck Ebbert
  -- strict thread matches above, loose matches on Subject: below --
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=47694FCC.1020507@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.