Package: apt-proxy
Version: 1.9.28

In trying to update package lists from client machine (using apt 0.6x)
using either "apt-get update" or "aptitude update" large package files
appear to continually download upon rerunning of "apt-get update", as if
they are not properly being cached.

Looking at the logs then:

2005/04/06 17:20 WST [Channel,153,192.168.5.66] [debug] Headers: Host:
aptproxy:
9999, Connection: keep-alive, If-Modified-Since: Wed, 06 Apr 2005 07:33:39
GMT, User-Agent: Debian APT-HTTP/1.3
2005/04/06 17:20 WST [Channel,153,192.168.5.66] [debug] Request: GET
/ubuntu/dists/hoary/universe/binary-i386/Packages.bz2
2005/04/06 17:20 WST [Channel,153,192.168.5.66] [Fetcher.activate]
(ubuntu) servers:1/ubuntu/dists/hoary/universe/binary-i386/Packages.bz2
2005/04/06 17:20 WST [Channel,153,192.168.5.66] [file_ok] check_cached:
/core/bank2/debian-proxy/ubuntu/dists/hoary/universe/binary-i386/Packages.bz2
2005/04/06 17:20 WST [Channel,153,192.168.5.66] [debug] starting
verification: /usr/bin/bunzip2 ('/usr/bin/bunzip2', '--test',
/core/bank2/debian-proxy/ubuntu/dists/hoary/universe/binary-i386/Packages.bz2')
2005/04/06 17:20 WST [-] [verify] Process Timedout:


The apt-proxy server machine is called "aptproxy" and is listening on the
default port "9999".  The client machine is an Ubuntu Linux (Hoary RC)
machine called "mooper" at address 192.168.5.66, following the log above,
so far all looks good.

It can be seen that the Packages.bz2 file is requested by the client, the
server picks up the request, finds a local cached copy and starts a
verification of the file integrity.  Not long after this though, only
seconds in fact as can be seen from the timestamp, the verification
process fails with a "Process Timedout"

The server thinks that the file has failed verification:

2005/04/06 17:20 WST [-] [verify] verification failed:
/core/bank2/debian-proxy/ubuntu/dists/hoary/universe/binary-i386/Packages.bz2


Doing a manual check of the Packages.bz2 file appears to indicate that the
file has compressed correctly without error:

[EMAIL 
PROTECTED]:/core/bank2/debian-proxy/ubuntu/dists/hoary/universe/binary-i386
# bunzip2 --test -vvv Packages.bz2
  Packages.bz2:
    [1: huff+mtf rt+rld {0x424035fb, 0x424035fb}]
    [2: huff+mtf rt+rld {0xb5a8991c, 0xb5a8991c}]
    [3: huff+mtf rt+rld {0x992bba37, 0x992bba37}]
    [4: huff+mtf rt+rld {0x152bfb07, 0x152bfb07}]
    [5: huff+mtf rt+rld {0x662ea75d, 0x662ea75d}]
    [6: huff+mtf rt+rld {0x11dfc5b6, 0x11dfc5b6}]
    [7: huff+mtf rt+rld {0x334dd35d, 0x334dd35d}]
    [8: huff+mtf rt+rld {0x94b123ed, 0x94b123ed}]
    [9: huff+mtf rt+rld {0x3b4f9bce, 0x3b4f9bce}]
    [10: huff+mtf rt+rld {0x41092dc0, 0x41092dc0}]
    [11: huff+mtf rt+rld {0xfff4a55b, 0xfff4a55b}]
    [12: huff+mtf rt+rld {0x181c9623, 0x181c9623}]
    [13: huff+mtf rt+rld {0x385f3890, 0x385f3890}]
    combined CRCs: stored = 0x7198fe0f, computed = 0x7198fe0f
    ok
[EMAIL 
PROTECTED]:/core/bank2/debian-proxy/ubuntu/dists/hoary/universe/binary-i386
#


My own feeling on this is that the server is quite old (Pentium classic
133MHz) and its taking longer than expected to test the Packages.bz2 file:

real    0m18.716s
user    0m18.368s
sys     0m0.156s

This output obtained from the '/usr/bin/time'

I had a look at the python source for apt-proxy, but am not a python
programmer and couldn't find where the default timeout for the bzip
verification is stored/initialised).  If you could point me to this I'll
happily change things in the source and fool about a bit to prove or
disprove my theory.

Note that this problem only appears to manifest on with clients requesting
.bz2 format Packages files - Debian testing does not show any problems as
it still uses the gzip format.  Ubuntu (Warty) also does not show the
problem up (apt version <0.6x).

Happy to do any testing you think is appropriate.

Best regards,
Craig



-- 
==============================================================
Craig Sampson
Senior Engineer
Professional Systems Integration Pty Ltd

PH 9397 5612
FX 9397 6031
==============================================================


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to