Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Jul 2004 10:43:20 -0700
From:      Matt White <>
Subject:   RE: fetch hangs, part 2
Message-ID:  <3270557515.1090406600@[]>
In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud>
References:  <000001c46f11$1f53a880$132a15ac@spud>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
In my case, I tracked this down to either my netscreen5 or the cable into 
it going south.  It's a bit strange because other software wasn't having an 
issue, so I'll probably look at this more in the next few days.  But for 
now, removing that box from my network has made fetch happy again, which in 
turn has made me happy again.


--On Wednesday, July 21, 2004 3:54 AM -0700 Darren Pilgrim 
<> wrote:

>> From: Robert Watson []
>> On Tue, 20 Jul 2004, Darren Pilgrim wrote:
>> > I've been having the same (or a similar problem).  Fetching the
>> > distfile for a port will hang.  I poked some more at this and found
>> > that all the sites fetch is hanging on successfully negotiate the TCP
>> > connection then go dead without closing the connection.  My workaround
>> > has been to edit the Makefile and remove the offending site from
>> > MASTER_SITES or manually fetch from
>> Could you try disabling TCP SACK
> Set net.inet.tcp.delayed_ack=0?
>> and see if things "get better"?  It's one
>> of the things that has changed in the TCP code recently.  This could well
>> be a user space fetch issue, but it would be worth trying it to see, if
>> only to rule it out.
> It didn't change.  The connections still hung.

Want to link to this message? Use this URL: <>