[Resending Aug 10 message where I forgot to Cc the bug address.] On Sun, Aug 05, 2012 at 12:20:07PM +0200, Eduard Bloch wrote:
> * Andras Korn [Thu, Aug 02 2012, 10:16:41PM]: > > Package: apt-cacher-ng > > Version: 0.7.6-1 > > Seriously? The messages below say that it's 0.7.4, not 0.7.6! Sorry, I'm filing the bug on one box and running apt-cacher on several boxes. The problem manifests both with 0.7.4 and 0.7.6. > And where is the config? Here is one: CacheDir: /var/cache/apt-cacher-ng LogDir: /var/log/apt-cacher-ng Port:4128 Remap-debrep: file:deb_mirror*.gz file:backends_debian /ftp.debian.org/debian/ /cdn.debian.net/debian/ /debian.mirrors.crysys.hu/debian/ /debian ; http://ftp.at.debian.org/debian/ http://cdn.debian.net/debian/ http://ftp.hu.debian.org/debian/ file:backends_debian ; keyfile=Release keyfile=.deb Remap-uburep: file:ubuntu_mirrors file:backends_ubuntu /ubuntu ; http://hu.archive.ubuntu.com/ubuntu/ http://at.archive.ubuntu.com/ubuntu/ file:backends_ubuntu ; keyfile=Release keyfile=.deb Remap-debsec: /security.debian.org/ /ftp.hu.debian.org/debian-security/ /debian-security ; http://security.debian.org/ ; keyfile=Release keyfile=.deb keyfile=Packages keyfile=Packages.bz2 keyfile=Sources keyfile=Sources.bz2 Remap-debbackports: /backports.org/debian/ /debian-backports ; http://backports.org/debian/ Remap-debpeople: /people.debian.org/ /debian-people ; http://people.debian.org/ Remap-debmultimedia: /debian-multimedia file:marillat_mirrors ; file:marillat_mirrors Remap-skype: /download.skype.com/linux/repos/debian /skype ; http://download.skype.com/linux/repos/debian/ Remap-opera: /deb.opera.com/opera /opera ; http://deb.opera.com/opera/ Remap-volatile: /volatile.debian.org/debian-volatile/ /ftp2.de.debian.org/debian-volatile/ /debian-volatile ; http://volatile.debian.org/debian-volatile/ http://ftp2.de.debian.org/debian-volatile/ Remap-debsnap: /snapshot.debian.net /debian-snapshot ; http://snapshot.debian.net/ Remap-canonical: /archive.canonical.com/ubuntu /canonical ; http://archive.canonical.com/ubuntu/ Remap-grml: http://deb.grml.org/ /grml ; http://deb.grml.org/ Remap-igraph: http://cneurocvs.rmki.kfki.hu/ /igraph ; http://cneurocvs.rmki.kfki.hu/ Remap-debunofficial: http://ftp.debian-unofficial.org/debian/ /debian-unofficial ; http://ftp.debian-unofficial.org/debian/ Remap-backports: http://www.backports.org/debian /backports ; http://www.backports.org/debian/ Remap-gosa: http://oss.gonicus.de/debian /gosa ; http://oss.gonicus.de/debian/ Remap-virtualbox: http://download.virtualbox.org/virtualbox/debian /virtualbox /vbox ; http://download.virtualbox.org/virtualbox/debian ReportPage: acng-report.html ForeGround: 0 ForceManaged: 0 ExTreshold: 5 ExAbortOnProblems: 0 MaxStandbyConThreads: 4 MaxConThreads: 48 LogSubmittedOrigin: 1 NetworkTimeout: 15 On another server, I have the same, except: -Remap-debrep: file:deb_mirror*.gz file:backends_debian /ftp.debian.org/debian/ /cdn.debian.net/debian/ /debian.mirrors.crysys.hu/debian/ /debian ; http://ftp.at.debian.org/debian/ http://cdn.debian.net/debian/ http://ftp.hu.debian.org/debian/ file:backends_debian ; keyfile=Release keyfile=.deb +Remap-debrep: file:deb_mirror*.gz /ftp.debian.org/debian/ /cdn.debian.net/debian/ /debian.mirrors.crysys.hu/debian/ /debian ; http://ftp.at.debian.org/debian/ http://cdn.debian.net/debian/ http://ftp.hu.debian.org/debian/ http://ftp.at.debian.org/debian/ http://ftp.kfki.hu/linux/debian/ http://ftp.externet.hu/debian/ ; keyfile=Release keyfile=.deb -Remap-uburep: file:ubuntu_mirrors file:backends_ubuntu /ubuntu ; http://hu.archive.ubuntu.com/ubuntu/ http://at.archive.ubuntu.com/ubuntu/ file:backends_ubuntu ; keyfile=Release keyfile=.deb +Remap-uburep: file:ubuntu_mirrors /ftp.hu.debian.org/ubuntu/ /ubuntu ; http://hu.archive.ubuntu.com/ubuntu/ http://at.archive.ubuntu.com/ubuntu/ http://ftp.kfki.hu/linux/ubuntu/ ; keyfile=Release keyfile=.deb > > It seems to me that in this case, tools like apt-get and debootstrap would > > try Packages.gz and Packages.bz2 as well (which do exist), but the 500 error > > throws them off. > > Your guess is close but I think it's another thing. The "Bad mirror" > code is generated by the code that attempts to detect a mirror with > missing architecture. The skipping of other Packages files would also be > enforced by that code. But this method only becomes active if you have > used the keyfile=... keyword in your config. Have you? Yes, see above. > > Resolving aptcacher (aptcacher)... 192.168.0.254 > > Connecting to aptcacher (aptcacher)|192.168.0.254|:3142... connected. > > HTTP request sent, awaiting response... > > HTTP/1.1 500 Bad mirror > > Content-Length: 144 > > Content-Type: text/html > > Date: Thu Aug 2 19:36:51 2012 > > Server: Debian Apt-Cacher NG/0.7.6 > > Connection: Keep-Alive > > 2012-08-02 21:36:51 ERROR 500: Bad mirror. > > > > This is what happens when I query it directly instead of going through > > Squid. I suppose Squid discards "Bad mirror" and returns "Internal Server > > Error" based on an internal table of HTTP status codes. > > > > Is there a good reason why the client is not allowed to see the 404 error? > > Please ask Squid or APT guys! What do they have to do with this? It's ACNG that sends the client a 500 error instead of a 404 error. > The problem with wrappers like Squid is the use of persistent connections > for multiple client requests. This is usually ok unless the remote host > (here: apt-cacher-ng) tries to do clever things based on the connection > identity. In your case, I can imagine a scenario where you there is a > mirror list where some mirrors only contain files for arch A and others > for arch B. And you have different clients in your LAN, so the first > client (arch A) tells acng to blacklist mirrors not having arch A and the > next client requires arch B which is unfortunately not available on any > mirrors that have arch A. Unlikely. I only have i386 and amd64 clients and the mirrors I prefer have both architectures; also, my test client was the only one accessing ACNG (I restarted ACNG before obtaining the error messages). > > Even if that error can't be passed through to the client for whatever > > reason, I think the error message ACNG returns could be improved. The error > > log isn't very informative either (and this is with Debug:4): > > Hard to find the right message which does not spam regular usage > output... I will change it to "500 Keyfile missing, mirror blacklisted". That's already a lot more useful (it points to keyfile and indicates that the mirror will be blacklisted from now). However, if this is how keyfile works, it doesn't do what I think it should do. Part of my reason for using apt-cacher-ng is to hide problems with mirrors from clients. I'd like apt-cacher-ng to try obtaining the keyfile from a different mirror instead of throwing an error at the client. Andras -- Andras Korn <korn at elan.rulez.org> At the Electric Company: "We would be delighted if you sent in your payment. However, if you don't, you will be." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
