Hallo, * Daniel Richard G. [Sat, May 14 2016, 11:56:40AM]: > 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 Yes, they are gone. And the expiration algorithm should to ignore them if a better version is found, i.e. Packages.xz. Just like apt does. Such files are also stored there when the pdiff patcher recreated a copy using pdiff patches so the next run can take this version as base for patching. Do you see any problem with that files? > 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 > 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. Maybe because it's arm64 and many mirrors don't contain it? Do have arm64 clients? Please share more information: which mirror, what's else inside of your cache ("find /var/cache/apt-cacher-ng"). The new extension in 0.9.2 identifies a by-hash/... file referenced by InRelease file then it creates an empty file there. This is designed specially for the case where user installs xenial with their recent apt which does not bother to download Packages.xz from the original location so the file is not created ever (not visible to proxy) and eventually cache maintenance starts cleaning "unreferenced" stuff. > 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. "touching" means what touch(1) does. > 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 Please send the resulting web page, my crystal ball is broken. > 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! Checkbox is displayed only once per file, maybe you needed to scroll up to find the first one? > I ended up deleting these files from the cache manually, but as soon as > I ran another scan, there they were again. Correct. That's why I would like to see what exactly was found in your cache. Regards, Eduard.
