199.232.138.132 (debian.map.fastlydns.net:80) is often failing last days
Uladzimir Bely <[email protected]> Wed, 05 Oct 2022 08:51:59 +0300
| Newsgroups | gmane.linux.debian.user.mirrors |
|---|---|
| Message-ID | <6803000.9J7NaK4W3v@hp> |
Hello all Our CI (server in Germany) builds several Debian-based images every day. Recently (for at least last 3 days) we often see that apt can't connect to Debian mirrors. E.g.: 06:32:07 INFO | | Need to get 11.6 MB/172 MB of archives. 06:32:07 INFO | | After this operation, 740 MB of additional disk space will be used. 06:32:07 INFO | | Get:1 copy:/<<RESOLVERDIR>>/apt_archive ./ sbuild-build- depends-main-dummy 0.invalid.0 [916 B] 06:32:07 INFO | | Err:2 http://deb.debian.org/debian bullseye/main armhf libasan6 armhf 10.2.1-6 06:32:07 INFO | | Could not connect to debian.map.fastlydns.net:80 (199.232.138.132), connection timed out Unable to connect to deb.debian.org:http: 06:32:07 INFO | | Err:3 http://deb.debian.org/debian bullseye/main armhf libatomic1 armhf 10.2.1-6 06:32:07 INFO | | Unable to connect to deb.debian.org:http: In sources.list* `http://deb.debian.org/*` is used, and in our case it is resolved as 199.232.138.132 that seems to be a German instance of debian.map.fastlydns.net. Had someone else experienced the similar problems with "Fastly" mirrors recently? What could be the best way to deal with the issue? Ideally, without changing the mirrors in source.list*.