On Thu, Aug 31, 2017 at 12:44:41PM -0700, michael goff wrote: > Package: apt-cacher > Version: 1.7.10+deb8u2 > Severity: important > > Dear Maintainer, > > Greetings, I have the most current apt-cacher in the raspbian repository, > using armhf. > I found ticket #755184 which seems to be the same problem but reported at a > different version number. > When trying to perform apt-get on a large package that is not in the cache > the download will begin then fail and start over again, repetedly. > doing tail on the error file and watch on the file being downloaded the error > msg happens at the same time as the file size being reset to 0B. > Wed Aug 30 02:07:26 2017|info [9904]: ALARM! > /mnt/addon/apt-cacher-cache/packages/archive.raspberrypi.org_debian/wolfram-engine_11.0.1+2017031701_armhf.deb > file size mismatch (found 5259264, expected 240084788). Renaming to > /mnt/addon/apt-cacher-cache/packages/archive.raspberrypi.org_debian/wolfram-engine_11.0.1+2017031701_armhf.deb.corrupted.
Michael, If this occurs with any large file it is different to #755184 (which is fixed AFAIK). Are you sure there is enough space on the partition to cache a 240MB package? If there is enough free space, can you send /var/log/apt-cacher/error.log with debugging enabled for a single file. You can use wget to do a single manual file request. > I have squid and apt-cacher installed on the same server, at first I thought > they were in conflict but with further anylsis squid is not involved at all. I > tried to route the traffic through squid using http_proxy = 127.0.0.1:8080 and > 127.0.0.1:80 and 10.1.0.1:8080 and 10.1.0.1:80 but all of those attempts > received a 503. Can apt-cacher use squid on the same server? Yes, I have used apt-cacher with an upstream cache with no problems. > I would like to > use this feature while this bug is being looked at, maybe even > perminently. What am I doing wrong with that? I changed the squid port to 8080 > btw. The private address the server uses is 10.1.0.1. If you have changed squid to 8080 then :80 won't work. You need to see if apt-cacher is returning the 503 or if squid is not configured correctly. Do a single request both to squid directly and through apt-cacher using something that will show you the response headers (HEAD, wget -S etc.) > The problem is reproducable on any large file. Define large. What is the threshold to trigger it? Mark
