Your message dated Wed, 9 Sep 2020 15:42:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#961594: Connection failed [IP: 151.101.112.204 80]
has caused the Debian Bug report #961594,
regarding Connection failed [IP: 151.101.112.204 80]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
961594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961594
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mirrors,apt
Severity: normal
On the apt.postgresql.org buildds, I've repeatedly seen failures when
retrieving files from security.debian.org. It started a few weeks ago,
and stopped when I reported the problem on #debian-mirrors on the 20th
when jcristau modified some SRV records for the originating network.
(The problem was seen from a Hetzner host in 78.46.0.0/15 aka
HETZNER-RZ-NBG-BLK5).
Now the problem is back, this time from Hetzner 144.76.0.0/16
HETZNER-RZ-BLK-ERX1.
26 11:58 <Myon> 11:53:34 Err http://security.debian.org/debian-security
stretch/updates/main
amd64 libldap-common all 2.4.44+dfsg-5+deb9u4
26 11:58 <Myon> 11:53:34 Connection failed [IP: 151.101.112.204 80]
26 11:58 <Myon> jcristau: it happened again
26 11:59 <Myon> this time from 144.76.0.0/16 HETZNER-RZ-BLK-ERX1
26 12:18 <jcristau> hmm there's 2 places apt seems to say "Connection failed",
one is closed
connection while getting headers, i can't quite figure out
the other one
26 12:19 <jcristau> Myon: can you file a bug against mirrors,apt so we can get
input from the
apt folks? i'm not sure i can usefully escalate to fastly
just yet
26 14:46 <Myon> if a bug with these two lines is enough, sure
26 14:46 <Myon> curious why it's always that .deb, bad cache?
26 14:47 <Myon> or maybe one bad backend?
26 14:49 <jcristau> yeah i don't know :/
Christoph
--- End Message ---
--- Begin Message ---
The problem is rare now, but I've seen it again a few weeks ago.
Afaict it was always with security packages.
I'm closing the bug now because it's of little use to keep a
non-actionable item open. Still unsure where the problem is, could as
well be on my end.
Christoph
--- End Message ---
