'apt update' failure, me or repository?
Greetings:
I've been seeing 'apt update' failures since yesterday:
# apt update
Err:1 http://ftp.us.debian.org/debian stable InRelease
Connection failed [IP: 128.61.240.89 80]
Err:2 http://security.debian.org/debian-security buster/updates InRelease
Connection failed [IP: 151.101.184.204 80]
Err:3 http://ftp.debian.org/debian buster-backports InRelease
Connection failed [IP: 130.89.148.12 80]
Err:4 http://ftp.us.debian.org/debian buster-updates InRelease
Connection failed [IP: 208.80.154.15 80]
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stable/InRelease Connection failed [IP: 128.61.240.89 80]
W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease Connection failed [IP: 151.101.184.204 80]
W: Failed to fetch http://ftp.us.debian.org/debian/dists/buster-updates/InRelease Connection failed [IP: 208.80.154.15 80]
W: Failed to fetch http://ftp.debian.org/debian/dists/buster-backports/InRelease Connection failed [IP: 130.89.148.12 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
#
But from the same host:
# wget http://ftp.us.debian.org/debian/dists/stable/InRelease && head -10 InRelease
--2019-10-15 15:23:16-- http://ftp.us.debian.org/debian/dists/stable/InRelease
Resolving ftp.us.debian.org (ftp.us.debian.org)... 64.50.233.100, 64.50.236.52, 208.80.154.15, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|64.50.233.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 121525 (119K)
Saving to: ‘InRelease’
InRelease 100%[===================>] 118.68K 690KB/s in 0.2s
2019-10-15 15:23:16 (690 KB/s) - ‘InRelease’ saved [121525/121525]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Origin: Debian
Label: Debian
Suite: stable
Version: 10.1
Codename: buster
Changelogs: http://metadata.ftp-master.debian.org/changelogs/@CHANGEPATH@_changelog
Date: Sat, 07 Sep 2019 09:51:20 UTC
To rule out the usual suspects:
1. There is no HTTP proxy involved, and none configured in
/etc/apt/*
2. The versions of Debian involved are 8, 9, and 10.
3. There are multiple networks and DNS servers involved.
4. Emptying /var/lib/apt/lists/ changes nothing.
5. Changing the mirror to two of those suggested by netselect-apt
changes only the names/IP addresses in the error messages.
6. One of the hosts is a brand new machine, just built, and with
only an untwiddled base install of 10.1 for AMD64.
I'm stumped. Can anyone tell me if this is something that I can fix, and
how I might go about it?
--
Art Sackett
http://www.artsackett.com/
Reply to: