-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Apr 20, 2018 at 10:20:12PM +0200, Rainer Dorsch wrote: > Am Freitag, 20. April 2018, 22:13:11 CEST schrieb to...@tuxteam.de: > > curl -I http://security.debian.org/debian-security/ > > root@master:~/tmp# curl -I http://ftp.de.debian.org/debian/ > HTTP/1.1 200 OK > Date: Fri, 20 Apr 2018 20:19:14 GMT > Server: Apache/2.4.10 (Debian) > Content-Type: text/html;charset=UTF-8 > > root@master:~/tmp# curl -I http://security.debian.org/debian-security/ > HTTP/1.1 200 OK
[...] Yeah, that succeeded *once*, but you suggested that your problem is intermittent. Either your network connection is sometimes down (you might see traces of that in your system log) or security.debian.org is sometimes down (somewhat less probable, since more folks would complain), or "something" in the path between you two is sometimes down. To catch this "sometimes" you'll have to invest a bit more of work. I'd start by looking into syslog, around the times your upgrade complains. Next, you might want to watch connectivity -- there sure are nice programs out there, with graphing and things, but just pinging your upstream router every minute might give you a rough impression, like so: ping -i 60 <your upstream router here> > /tmp/connect.log 2>&1 & and have look at the result after a day or so. If you're on WiFi, check for bad signal quality or too many nearby routers (or other sources of noise). If it's Ethernet, flakey cables or connectors are known for doing nasty things. And so on. It's a bit like hunting :-) Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlra3YgACgkQBcgs9XrR2kaS1wCfcfX3VDhq9X7azonwDojhjvL9 K5YAn2YyuMsIWQ535uR3L5S9ApZ2Ocmc =nnfe -----END PGP SIGNATURE-----
