204.152.191.39 & reprepro do not play well together
Hi,
I've had a mirror communication issue for some time now but only with
one mirror. The typical scenario is to do an "initial" reprepro update
which downloads just about all of the updates, I assume from various
IPs. However there usually is at least one error in the job. If I do
another (and another ad infinitum), I'll get something similar
(depending upon the day I update) to the below:
% reprepro -v --ask-passphrase update squeeze
WARNING: Updating does not update trackingdata. Trackingdata of squeeze
will be outdated!
aptmethod got 'ftp://ftp.us.debian.org/debian/dists/squeeze/Release'
aptmethod got 'ftp://ftp.us.debian.org/debian/dists/squeeze/Release.gpg'
Calculating packages to get...
nothing new for blahblahblah [snip nothing news]
Getting packages...
aptmethod error receiving
'ftp://ftp.us.debian.org/debian/pool/main/a/agedu/agedu_8928-1.dsc':
'Server closed the connection [IP: 204.152.191.39 21]'
Shutting down aptmethods...
There have been errors!
If I force reprepro to go to a specific IP (35.9.37.225 in this case),
then it works though skipping the missing package, e.g.
% reprepro -v --ask-passphrase update squeeze
WARNING: Updating does not update trackingdata. Trackingdata of squeeze
will be outdated!
aptmethod got 'ftp://35.9.37.225/debian/dists/squeeze/Release'
aptmethod got 'ftp://35.9.37.225/debian/dists/squeeze/Release.gpg'
aptmethod got
'ftp://35.9.37.225/debian/dists/squeeze/non-free/source/Sources.gz'
aptmethod got
'ftp://35.9.37.225/debian/dists/squeeze/non-free/binary-i386/Packages.gz'
aptmethod got
'ftp://35.9.37.225/debian/dists/squeeze/main/source/Sources.gz'
aptmethod got
'ftp://35.9.37.225/debian/dists/squeeze/main/binary-i386/Packages.gz'
aptmethod got
'ftp://35.9.37.225/debian/dists/squeeze/main/binary-powerpc/Packages.gz'
Calculating packages to get...
nothing new for blahblahblah [snip nothing news]
Getting packages...
Shutting down aptmethods...
Installing (and possibly deleting) packages...
So, my conclusion is that there is something strange going on with
204.152.191.39 .
-jeff
Reply to: