On Tue, Mar 25, 2008 at 09:23:10AM -0700, Ross Boylan wrote: > Package: apt-cacher > Version: 1.6.1 > Severity: normal > > My nightly cron job failed with > ----------------------------------------- > /etc/cron.daily/apt-cacher: > Unable to update /mainline/dists/testing/main/source/Sources.bz2 . Network > problems? > Run /usr/share/apt-cacher/apt-cacher-cleanup.pl with -v to get more details. > Cleanup aborted since cached data may be damaged. > run-parts: /etc/cron.daily/apt-cacher exited with return code 4 > ----------------------------------------- > > When I ran > ------------------------------------------------------------ > corn:/# /usr/share/apt-cacher/apt-cacher-cleanup.pl -v > Invoked as root, changing to www-data:www-data and re-execing. > # ...... > GET /mainline/dists/testing/main/binary-i386/Packages.bz2 > GET /mainline/dists/testing/main/source/Sources.bz2 > Unable to update /mainline/dists/testing/main/source/Sources.bz2 . Network > problems? > Run /usr/share/apt-cacher/apt-cacher-cleanup.pl with -v to get more details. > Cleanup aborted since cached data may be damaged. > -------------------------------------------------------------- > > Since the run was a couple hours after the nightly job, and since all > the other files transferred OK, it seems unlikely it is a network > problem. > > I poked around the cache. The only thing I noticed was that private/ > has a 711 byte file > mainline_dists_testing_main_source_Sources.bz2.notify. > > The error message, particularly the advice to use -v when run with -v, > doesn't seem too helpful.
Certainly that is true. I have already changed it in version 1.6.2 which I am doing final tests on now. Has the error gone away? It is pretty non-specific. It is really there to prevent the cache being emptied by intermittent errors in updating the index files. Or am I missing your particular concern? Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
