Package: apt-cacher-ng
Version: 0.9.2-1
Previously, with 0.9.1-1, I have been getting these e-mails daily:
/etc/cron.daily/apt-cacher-ng:
Maintenance Task: Expiration
See file /var/log/apt-cacher-ng/maint_1463136764.log.html for more
details.
Server url:
http://localhost:3142//acng-report.html?doExpire=Start+Expiration&abortOnErrors=aOe
Problem with debian/dists/sid/main/binary-amd64/Packages
Problem with debian/dists/sid/main/binary-armel/Packages
Problem with debian/dists/sid/non-free/binary-amd64/Packages
Problem with debian/dists/sid/non-free/binary-armel/Packages
This was no big deal, a case of index files actually disappearing on the
upstream server. (I had real content and .head files for these in the
cache, with recent timestamps.) I was going to write in to request
better automagic handling of this situation, since I eventually had to
go in and delete these files on the expiration page to stop the e-mails.
(I figure, if you can download other things from that server, those 404s
are unlikely to be transient.)
However, I upgraded to 0.9.2-1 for the by-hash goodness, and now I see
this in my inbox:
/etc/cron.daily/apt-cacher-ng:
Maintenance Task: Expiration
See file /var/log/apt-cacher-ng/maint_1463222283.log.html for more
details.
Server url:
http://localhost:3142//acng-report.html?doExpire=Start+Expiration&abortOnErrors=aOe
Problem with
ubuntu-security/dists/xenial-security/restricted/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu-security/dists/xenial-security/multiverse/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu-security/dists/xenial-security/universe/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/multiverse/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/restricted/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-updates/multiverse/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-updates/restricted/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/universe/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu-security/dists/xenial-security/restricted/binary-arm64/Packages.xz
Problem with
ubuntu-security/dists/xenial-security/multiverse/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial/restricted/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial/multiverse/debian-installer/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/multiverse/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/restricted/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-updates/restricted/binary-arm64/Packages.xz
Problem with
ubuntu/dists/xenial-updates/multiverse/binary-arm64/Packages.xz
Problem with ubuntu/dists/xenial/restricted/binary-arm64/Packages.xz
Problem with
ubuntu-security/dists/trusty-security/multiverse/debian-installer/binary-arm64/Packages.gz
Problem with
ubuntu-security/dists/trusty-security/restricted/debian-installer/binary-arm64/Packages.gz
Problem with
ubuntu-security/dists/xenial-security/restricted/debian-installer/binary-arm64/Packages.gz
Problem with
ubuntu-security/dists/xenial-security/multiverse/debian-installer/binary-arm64/Packages.gz
Problem with
ubuntu-security/dists/xenial-security/universe/debian-installer/binary-arm64/Packages.gz
Problem with
ubuntu-security/dists/xenial-security/restricted/debian-installer/binary-armhf/Packages.xz
Problem with
ubuntu-security/dists/xenial-security/multiverse/debian-installer/binary-armhf/Packages.xz
Problem with
ubuntu-security/dists/xenial-security/universe/debian-installer/binary-armhf/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/restricted/debian-installer/binary-armhf/Packages.xz
Problem with
ubuntu/dists/xenial-proposed/multiverse/debian-installer/binary-armhf/Packages.xz
Problem with
ubuntu/dists/xenial-updates/multiverse/debian-installer/binary-armhf/Packages.xz
[...]
(That's about one-fifth of the message.)
Unlike the previous situation, none of these index files exist on the
upstream server. I only have empty files (and no .head file) for each.
I did recall seeing during a manual scan/expiration shortly after
installing 0.9.2 that acng was "touching" a lot of index files. I
suspect it was doing so in the sense of creating empty files rather than
just updating timestamps.
And if that weren't enough, when I went to the expiration page and hit
"Check all" and then "Delete selected" to clean up this mess, the
resulting list on the confirmation page included numerous valid index
files for amd64/i386---even though they did exist upstream, had been
downloaded correctly, and did not have a "Tag" checkbox on the
expiration page. It was even going to delete files like
ubuntu/dists/xenial/Release!
I ended up deleting these files from the cache manually, but as soon as
I ran another scan, there they were again.
