apt-proxy-users

[Apt-proxy-users] Problems on a 28.8kbps link

[Thomas A. <tan...@gr...>]

I need some help to sort out this bizarre error condition which seems to
be directly related to the speed at which I can download. Apt-proxy's
Packages.gz files get corrupted every time the mirror changes - not all of
them - just one or two. The only way I can fix the problem is to change
BACKEND_FREQ=240 to BACKEND_FREQ=2 so that it forces a re-fetch of the
Package lists, which in turn finds the ones that are truncated.

It almost feels like something is getting tired of waiting, so it gives
up, and doesn't finish the download. Is it maybe possible to get
apt-proxy to download files one after the other, rather than in
parallel? Sort of force it to finish one job at a time... 

I don't think it's apt-get at fault because once it's broken it repeats
the pattern verbatim - just much quicker. Here are the details:


When I run apt-get update I get this:

8<---------------------------------------------------------------
slink:~# apt-get update
Get:1 http://gaspode.nextlink.co.za testing/main Packages [1129B]
98% [1 Packages gzip 0] [Waiting for file]
gzip: stdin: unexpected end of file
Err http://gaspode.nextlink.co.za testing/main Packages
  Sub-process gzip returned an error code (1)
Hit http://gaspode.nextlink.co.za testing/main Release
8<---------------------------------------------------------------


This is the matching snippet from /var/log/apt-proxy.log:

8<---------------------------------------------------------------
[23072 19:20:10]  Sun Sep 28 19:20:10 SAST 2003 Request /debian/dists/testing/main/binary-i386/Packages.gz
[23072 19:20:10]  Delivered partial file /var/cache/apt-proxy/debian/dists/testing/main/binary-i386/Packages.gz, from offset 0.

gzip: /var/cache/apt-proxy/debian/dists/testing/main/binary-i386/Packages.gz: unexpected end of file
[23072 19:20:11]  Sun Sep 28 19:20:11 SAST 2003 Request /debian/dists/testing/main/binary-i386/Release
8<---------------------------------------------------------------

Here's my config:

8<---------------------------------------------------------------
APT_PROXY_CACHE=/var/cache/apt-proxy
add_backend /debian/                                    \
        $APT_PROXY_CACHE/debian/                        \
        http://ftp.debian.org/debian/           \
        http://ftp.us.debian.org/debian/                \
        http://ftp.de.debian.org/debian/                \
        http://ftp.uk.debian.org/debian/                \
        +ftp.us.debian.org::debian/
add_backend /non-US/                                    \
        $APT_PROXY_CACHE/non-US/                        \
        http://non-us.debian.org/                       \
        http://ftp.de.debian.org/debian-non-US/         \
        http://ftp.uk.debian.org/debian-non-US/         \
        +ftp.de.debian.org::debian-non-US/
add_backend /security/                                  \
        $APT_PROXY_CACHE/security/                      \
        http://security.debian.org/
CLEANUP_DAYS=14
CLEAN_SWEEP=60
MAX_VERSIONS=2
BACKEND_FREQ=240
RSYNC_TIMEOUT=30
WGET_TIMEOUT=300
export http_proxy=http://localhost:8080/
export ftp_proxy=http://localhost:8080/
8<---------------------------------------------------------------

Turning on debugging info didn't add anything particularly useful (to me
anyway).

Many thanks,
Thomas

Re: [Apt-proxy-users] Problems on a 28.8kbps link

[Robert G. <rgu...@po...>]

The error you show below happens to me all of the time.  I usually just 
run "apt-get update" again and it fixes the problem on it's own.  I'm 
using the stable release of debian & the corresponding version of 
apt-proxy.


Your config settings look fine; have you tried increasing the value for 
RSYNC_TIMEOUT?  Seems a little short, and might have something to do 
with my own problems.  I'll start playing with it myself and see what I get.

Re: [Apt-proxy-users] Problems on a 28.8kbps link

[Thomas A. <tan...@gr...>]

On Tue, Sep 30, 2003 at 02:36:25PM -0500, Robert Guthrie wrote:

> Your config settings look fine; have you tried increasing the value for 
> RSYNC_TIMEOUT?  Seems a little short, and might have something to do 
> with my own problems.  I'll start playing with it myself and see what I get.

I've increased the timeouts (both) to 600, and it's made no difference.

I noticed something funny though: the whole process gives up and dies,
but still the modem lights flicker on and on. ps shows nothing so it's
not rsync that's busy - netstat indicates one remaining connection.

It's like the ftp/http session that's spawned is not communicating properly
back that it's still busy ???

The other slightly odd thing is that I sometimes see two instances of
rsync (with ps) both getting the same file. Does this make sense ? Does
it split into junks ?

-Thomas