Re: [Pgbuildfarm-members] Submission failures: 500 read timeout

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>
Subject: Re: [Pgbuildfarm-members] Submission failures: 500 read timeout
Date: 2014-09-22 09:59:25
Message-ID: CABRT9RCef4ssZ4pN-smj-wqcpRT1ktd8XvPpm24ziv8tc7xi5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members

On Mon, Sep 22, 2014 at 12:21 PM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:
>> data after receiving a SACK packet if the missing data isn't
>> acknowledged during the retransmit timeout.

> hard to say - but that description feels like a common problem going 10
> years backwards when stateful firewalls started doing sequence inspection
> and randomisation but were not yet SACK aware.

That could be an explanation, but AFAICT there is no evidence of that.
The SACK ranges match up to the packets retransmitted after the FIN,
and the eventual HTTP 200 response indicates that the remote did
reassemble the correct stream after receiving those packets. So I see
no reason to suspect middleboxes.

> It might be a long stretch but [...] _AND_
> there is a device on either side that has a slightly broken stateful
> inspection firewall

There's just a Juniper SRX100B doing NAT on my end, which isn't very
old and shouldn't have any paranoia settings enabled.

Regards,
Marti

In response to

Browse buildfarm-members by date

  From Date Subject
Next Message Tom Lane 2015-01-18 22:48:11 Reducing buildfarm disk usage: remove temp installs when done
Previous Message Stefan Kaltenbrunner 2014-09-22 09:21:41 Re: [Pgbuildfarm-members] Submission failures: 500 read timeout