On Sun, Feb 26, 2006 at 11:39:12AM +0100, Eduard Bloch wrote:
> tags 354428 + moreinfo
> thanks
>
> #include <hallo.h>
> * Ross Boylan [Sat, Feb 25 2006, 10:39:52PM]:
> > Package: apt-cacher
> > Version: 1.5.1
> > Severity: normal
> >
> > For at least several days I've been getting errors from aptitude and
> > apt-get about missing packages files; unfortunately testing/main is
> > one of them. apt doesn't seem to write the packages into its spots
> > (/var/lib/apt/lists). testing/non-free is the other missing file;
> > test/contrib is present.
> >
> > I find the corresponding packages files in apt-cacher's cache. bzip2
> > verifies they are corrupt, and their lengths are shorter than the file
> > in the original archive. I can download the latter via lftp; the
> > result is full length and verifies OK.
>
> Weird. In theory, there is an extra check to detect incompletely
> downloaded files, so apt-cacher should stop, close the connection and
> remove the broken file from the cache.
>
> > My efforts to trigger an update via aptitude update appear partly
> > successful; the timestamps on the file in apt-cacher's cache change.
> > But the file remains broken.
After I sent the message, I tried again, and this time the timestamps
(of the files packages files under packages/) didn't update. I don't
understand what all the different files and directories, or nor
the conditions under which they should update. I had the impression
that apt-cacher wouldn't update from the net more than once in 24
hours, though it's a fuzzy memory.
> >
> > Possibly this is related to running out of disk space, though it looks
> > as if there should be enough. /var did fill up a few days ago, maybe
> > around when this started.
I checked further and the problems began the day before the disk
(specifically /var; both apt and apt-cacher have dedicated partitions
for their big caches) filled. However, apt-cacher gets hit by an
overnight aptitude update job that runs while a backup is running.
The latter may use more space while it's running than when it completes.
> > Possibly the problem is related to issues
> > reported in 353152, and since fixed. Since my updates from main are
> > not working, it's hard to upgrade (:
>
> Not really, 353152 was about the file updates in the cleanup run.
I was noticing the complaints from bzcat, particularly in my addendum
to that bug report. The problems I reported there may not have been
related to the original, and it looks as if I'm seeing more of them.
Details below.
>
> > [EMAIL PROTECTED]:/usr/local/var/mirrors/apt-cacher/packages$ ls -l
> > linux.csua.berkeley.edu_debian_dists_testing_main_binary-i386_Packages.bz2
> > -rw-r--r-- 1 www-data www-data 2435536 2006-02-25 21:35
> > linux.csua.berkeley.edu_debian_dists_testing_main_binary-i386_Packages.bz2
> >
> > The file at Berkeley, is
> > lftp linux.csua.berkeley.edu:/debian/dists/testing/main/binary-i386> ls
> > -rw-r--r-- 1 103 65534 2850393 Feb 25 20:17 Packages.bz2
>
> Could you check the error.log file please?
/var/log/apt-cacher/error.log is empty; last time stamp Dec 29.
> Any serious issues reported
> (file corruption etc.). If you have enough disk space, consider enabling
> debugging (debug=1 in apt-cacher.conf) and if this happens again -
> report it.
I've enabled debugging and did a force-reload.
>
> I saw in your second message that you removed the broken file, that is
> just too bad since locating the problem is a bit complicated now.
>
> Eduard.
I could try manually truncating the file. If you'd like me to do
that, let me know. Please also let me know how I should test it
afterwords, e.g., if I need to wait 24 hours, wait til the relevant
file is updated in the archive ....
However, there seem to still be a bunch of problems. Let me first
mention one that isn't. After I deleted the file and updated, I also
checked whether the other damaged packages file (testing/contrib) was
OK. It was. Unfortunately, I didn't check its state before this
exercise (though there were the reports from apt-cacher).
My daily cleanup job is now showing
----------------------------------------------------
/etc/cron.daily/apt-cacher:
bzcat: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzcat: Success
Input file =
box2.squeakfoundation.org_files_debian_dists_unstable_main_binary-i386_Packages.bz2,
output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzcat: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzcat: Success
Input file =
box2.squeakfoundation.org_files_debian_dists_unstable_main_source_Sources.bz2,
output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzcat: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzcat: Success
Input file =
security.debian.org_dists_sarge_updates_contrib_binary-i386_Packages.bz2,
output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzcat: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzcat: Success
Input file =
security.debian.org_dists_sarge_updates_main_binary-i386_Packages.bz2, output
file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzcat: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzcat: Success
Input file =
security.debian.org_dists_sarge_updates_non-free_binary-i386_Packages.bz2,
output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In all the preceding cases, there is no .bz2 file in packages/, though
a .bz2.notify is in private/. Here's the file list for box2:
----------------------------------------------------
/usr/local/var/mirrors/apt-cacher/packages$ find .. -name 'box2*' -ls
6210 4 -rw-r--r-- 1 www-data root 2514 Jan 20 22:33
../packages/box2.squeakfoundation.org_files_debian_dists_unstable_main_binary-i386_Packages.gz
6213 4 -rw-r--r-- 1 www-data root 1576 Dec 29 18:43
../packages/box2.squeakfoundation.org_files_debian_dists_unstable_main_source_Sources.gz
6211 4 -rw-r--r-- 1 www-data root 367 Jan 20 22:33
../headers/box2.squeakfoundation.org_files_debian_dists_unstable_main_binary-i386_Packages.gz
6214 4 -rw-r--r-- 1 www-data root 367 Dec 29 18:43
../headers/box2.squeakfoundation.org_files_debian_dists_unstable_main_source_Sources.gz
154 4 -rw-r--r-- 1 www-data www-data 5 Feb 26 02:40
../private/box2.squeakfoundation.org_files_debian_dists_unstable_Release.notify
79 4 -rw-r--r-- 1 www-data www-data 6 Feb 26 07:36
../private/box2.squeakfoundation.org_files_debian_dists_unstable_main_binary-i386_Packages.bz2.notify
107 4 -rw-r--r-- 1 www-data www-data 6 Feb 26 07:37
../private/box2.squeakfoundation.org_files_debian_dists_unstable_main_source_Sources.bz2.notify
6215 4 -rw-r--r-- 1 www-data root 77 Dec 29 18:43
../private/box2.squeakfoundation.org_files_debian_dists_unstable_main_source_Sources.gz.complete
6212 4 -rw-r--r-- 1 www-data root 83 Jan 20 22:33
../private/box2.squeakfoundation.org_files_debian_dists_unstable_main_binary-i386_Packages.gz.complete
101 4 -rw-r--r-- 1 www-data www-data 5 Feb 26 02:40
../private/box2.squeakfoundation.org_files_debian_dists_unstable_Release.gpg.notify
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I think this is consistent with your remark that apt-cacher should
delete the file if there's trouble.
I've just updated to 1.5.2 from unstable. Looking in error.log so
far, I notice one oddity, the timeout message below:
--------------------------------------------------------------
Sun Feb 26 15:29:56 2006|127.0.0.1|debug [881]: fetcher: try to fetch
http://linux.csua.berkeley.edu/debian/pool/main/a/apt-cacher/apt-cacher_1.5.2_all.deb
Sun Feb 26 15:29:56 2006|127.0.0.1|debug [881]: download agent: getting
http://linux.csua.berkeley.edu/debian/pool/main/a/apt-cacher/apt-cacher_1.5.2_all.deb
Sun Feb 26 15:29:57 2006|127.0.0.1|debug [880]: abort (timeout)
Sun Feb 26 15:29:58 2006|127.0.0.1|debug [881]: Entering critical section :
Callback, storing the header
Sun Feb 26 15:29:58 2006|127.0.0.1|debug [881]: Exiting critical section
Sun Feb 26 15:29:58 2006|127.0.0.1|debug [881]: Get is back
Sun Feb 26 15:29:58 2006|127.0.0.1|debug [881]: stored
http://linux.csua.berkeley.edu/debian/pool/main/a/apt-cacher/apt-cacher_1.5.2_all.deb
as /usr/local/var/mirrors/apt-cacher/packages/apt-cacher_1.5.2_all.deb
Sun Feb 26 15:29:58 2006|127.0.0.1|debug [881]: setting complete flag for
apt-cacher_1.5.2_all.deb
Sun Feb 26 15:29:58 2006|127.0.0.1|debug [881]: fetcher exiting
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Since the file was retrieved, I don't know if it's significant (e.g.,
of timeouts that could be truncating the packages files on download).
Ross
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
