Hi, I've tried a number of servers and got the same results, however the traceroute to www.uk.debian.org times out as follows : traceroute www.uk.debian.org traceroute to debian.hands.com (83.142.228.128), 30 hops max, 40 byte packets 1 host-83-146-18-14.bulldogdsl.com (83.146.18.14) 50.965 ms 49.049 ms 47.947 ms 2 ge-2-0-0.31.cll-cor-002.bddsl.net (83.146.17.78) 50.463 ms 47.407 ms 45.960 ms 3 so-1-0-0.0.cht-cor-002.bddsl.net (83.146.19.46) 49.294 ms 49.573 ms 47.942 ms 4 so-0-1-0.0.cht-cor-001.bddsl.net (83.146.19.81) 50.477 ms 48.406 ms 50.965 ms 5 so-0-0-0.0.thn-cor-001.bddsl.net (83.146.19.153) 48.521 ms 46.356 ms 50.958 ms 6 ge0-1.linx.lon.rapidswitch.com (195.66.224.207) 50.536 ms 50.348 ms 48.949 ms 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * A traceroute wo www.debian.org ( which displays the same symptoms ) shows : traceroute www.debian.org traceroute to www.debian.org (192.25.206.10), 30 hops max, 40 byte packets 1 host-83-146-18-14.bulldogdsl.com (83.146.18.14) 52.332 ms 48.446 ms 46.968 ms 2 ge-2-0-0.30.cll-cor-001.bddsl.net (83.146.17.62) 48.361 ms 46.763 ms 47.944 ms 3 195.50.117.105 (195.50.117.105) 68.950 ms 134.761 ms 104.941 ms 4 ae-0-56.gar2.London1.Level3.net (4.68.116.172) 51.175 ms ae-0-54.gar2.London1.Level3.net (4.68.116.108) 47.765 ms 47.734 ms 5 sl-bb21-lon-6-0.sprintlink.net (213.206.131.21) 49.622 ms 159.736 ms 206.993 ms 6 sl-bb21-tuk-10-0.sprintlink.net (144.232.19.69) 117.877 ms 117.821 ms 117.937 ms 7 sl-bb20-tuk-15-0.sprintlink.net (144.232.20.132) 117.959 ms 117.774 ms 118.942 ms 8 sl-bb20-rly-11-0.sprintlink.net (144.232.20.136) 163.929 ms 304.753 ms 208.925 ms 9 sl-bb24-rly-9-0.sprintlink.net (144.232.14.122) 130.932 ms 130.781 ms 167.922 ms 10 sl-bb21-rly-10-0.sprintlink.net (144.232.14.145) 130.954 ms 130.746 ms 130.953 ms 11 sl-bb21-atl-6-0.sprintlink.net (144.232.20.176) 143.918 ms 143.764 ms 175.924 ms 12 sl-bb24-atl-9-0.sprintlink.net (144.232.12.30) 143.947 ms 148.788 ms 143.928 ms 13 sl-gw11-atl-10-0.sprintlink.net (144.232.12.90) 142.928 ms 143.773 ms 143.940 ms 14 sl-hp1-3-0.sprintlink.net (144.228.208.86) 145.933 ms 146.741 ms 143.941 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 gluck.debian.org (192.25.206.10) 183.489 ms 184.668 ms 182.921 ms I also have attached a file which failed ( I chose the smallest one I could find ) . It was located in the /var/cache/apt/archives/partial subdir. Hope this helps, Eamonn -----Original Message----- From: fw@deneb.enyo.de To: Eamonn Hamilton Cc: 364272@bugs.debian.org Sent: 4/23/2006 2:55 PM Subject: Re: Bug#364272: apt: recent difficxulty in updateing, "Remote end closed connection" and MD5 sum errors * Eamonn Hamilton: > I've been trying to get my system to reliably perform an apt-get update > and upgrade for the last three or four weeks. Symptoms seem to be that > it'll get to the last few K of a file, and then time out, the server > closes the connection or there's a checksum error. This could be a faulty along the network path to the Debian mirror (the TCP checksum does not guard against periodic bit errors when the period is an integer multiple of 16). Could you provide a traceroute to the Debian mirror you use and a copy of a file whose MD5 hash does not match?
Attachment:
vnc4-common_4.1.1+X4.3.0-7_i386.deb.FAILED
Description: Binary data