From: "James Nichols" <jamesnichols3@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: After many hours all outbound connections get stuck in SYN_SENT
Date: Tue, 18 Dec 2007 10:34:26 -0500 [thread overview]
Message-ID: <83a51e120712180734i334399dbl51f44fe32d815f7d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712180009390.32270@fbirervta.pbzchgretzou.qr>
> Try uploading something through rsync+ssh, or scp+ssh. If it aborts
> or hangs after a while, that may be an strong indication of a crappy
> router. Also, I'd advise to upgrade to something newer like >=
> 2.6.22. There was one of those SACK-broken routers around here too,
> but it seemed to have been replaced (or linux got a mysterious fix
> :-) as one day when I tried turning off SACK, rsync didnot abort
> anymore on new connections.
Uploads to hosts other then 2000 being hit by my app via webservices
run flawlessly to completion. I really don't think it is my routing
equipment- I've completely rebuilt the whole network infrastructure
several times in the 4 years that I've had this problem, have moved to
different colo facilities, and several other network related factors
and still have seen this problem.
It's very challenging for me to upgrade the kernel as this is a
production system and I need to run on whatever the latest RedHat
supports for support contract reasons. I probably could do it if
there are specific fixes that there is reason to believe will make my
problem go away.
> Though, if SACK was the problem, the problem would be much more
> likely to appear after the handshake. YMMV.
next prev parent reply other threads:[~2007-12-18 15:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 20:39 James Nichols
2007-12-17 23:14 ` Jan Engelhardt
2007-12-18 15:34 ` James Nichols [this message]
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
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 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
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=83a51e120712180734i334399dbl51f44fe32d815f7d@mail.gmail.com \
--to=jamesnichols3@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®