It seems that there are transient failures with
artifacts.elastic.co, perhaps servers that are out of sync. We sometimes see this when running
apt-get -q update:
$ sudo apt-get -q update ... Ign:5 https://artifacts.elastic.co/packages/5.x/apt stable InRelease Err:6 https://artifacts.elastic.co/packages/5.x/apt stable Release 404 Not Found [IP: 22.214.171.124 443] ... Reading package lists... E: The repository 'https://artifacts.elastic.co/packages/5.x/apt stable Release' no longer has a Release file.
$ sudo apt-get -q update ... Ign:8 https://artifacts.elastic.co/packages/5.x/apt stable InRelease Hit:9 https://artifacts.elastic.co/packages/5.x/apt stable Release
This can be reproduced with
$ curl --silent -D - https://artifacts.elastic.co/packages/5.x/apt/dists/stable/Release HTTP/2 404 server: nginx/1.17.8 date: Wed, 03 Mar 2021 19:07:19 GMT content-length: 9 strict-transport-security: max-age=15724800; includeSubDomains via: 1.1 google age: 20 alt-svc: clear
HTTP/2 200 server: nginx/1.17.8 date: Wed, 03 Mar 2021 19:07:00 GMT content-type: application/octet-stream content-length: 5116 last-modified: Tue, 19 Mar 2019 14:52:46 GMT etag: "f0c208efc3f994f168faa64cb26730e2" accept-ranges: bytes strict-transport-security: max-age=15724800; includeSubDomains via: 1.1 google age: 52 cache-control: public, max-age=120 alt-svc: clear Origin: elastic Label: . stable Suite: stable Codename: stable Date: Tue, 19 Mar 2019 14:51:51 UTC Architectures: amd64 i386 Components: main Description: Generated by aptly MD5Sum: 5fda4d0ec4ff29c476c1514390a778d8 635567 Contents-amd64.gz 5fda4d0ec4ff29c476c1514390a778d8 635567 Contents-i386.gz ...
I have enough hosts that I was able to make sure it wasn't a version of
apt or anything, and
curl shows that it isn't
apt-specific either. I tested out versions of tls1. and http1.1/http2.0 to ensure it wasn't a difference in those. Nope.
Another thought was that it had to do with the age of the elastic.co packages (5.x). However, two things disprove this. First, I've been able to run
curl and hit a bad host with each of the three versions (.x). Second, it's been reported by others on those versions too.
I'll link to this thread from the github issue. Even if this one doesn't get a reply, hopefully it'll help others who run into this issue and can't figure out why- TLDR: elastic.co has a problem.