#include <hallo.h> * Stuart Pook [Mon, Mar 23 2009, 10:00:46AM]: >>> Checking/Updating debrep/dists/squeeze/Release.gpg... >>> <br> >>> Error while redownloading this file!<br> Reason: Reason: HTTP/1.1 503 DNS >>> error: Name or service not known<br><br>Checking/Updating >>> debrep/dists/lenny/main/binary-i386/Packages.bz2... >> >> Here is your reason - your DNS config does not work when the update >> runs. Or there is a bad host which the daemon tries to connect, see >> below. > > My DNS works all the time. I have a permanent ADSL connection with a fixed > IP address. I have my own SMTP server for incoming email which works. The > apt-cacher-ng cron job runs as the same time as my other jobs such as > "apt-get update". They all work.
Ah, fine. > >> Then check the /etc/apt-cacher-ng/backends_* files where the remote >> servers are listed, because... > > I removed the debian backend file and reran "dpkg-reconfigure" (as suggested > on the wiki) and the debian backend file was recreated (empty I think). Which Wiki? How should I know what you mean? And why do you remove the stuff, did you at least look inside that file? Because the answer to your question is/was most likely inside. However, if it's empty then it's ok too. The backends file is created by picking previous sources from sources.list and guessing the appropriate remote mirror(s) for backend specification. All that stuff is optional and only important if the proxy is accessed with "simplified URLs", i.e. http://proxyHost/debian/... instead of http://proxyHost/ftp.XY.debian.org/debian/... ; if that's not relevant for you then just forget it. > Is the user meant to edit /etc/apt-cacher-ng/backends_*? I haven't found any > documentation on how to edit (correct?) these files. Huh? file:///usr/share/doc/apt-cacher-ng/html/config-serv.html#adv-map >> Fix your internet connection. > > NTP works, outgoing and incoming SMTP work, my asterisk server works, why is > apt-cacher-ng special? I don't know your setup in detail. Which hostname did it try to resolve? >> Does this reconnect happen >> at night at precisely that time when cron runs? > > No it happens even when I run the cron job by hand. Good if it's reproducible. >> OR: if there are unreliable hosts which you don't want to be tested, >> read in the manual about the ignore list, but this workaround should be >> used with care. > > If there are unreliable hosts they must be in one of the apt-cacher-ng > configuration files (that I have not edited). Why is apt-cacher-ng > configured with unreliable hosts? The only hosts that I have Huh? "If" means "if". I don't know what is/was inside of the backends file. > configured are in /etc/apt/sources.list and ftp.fr.debian.org is > reliable. Indeed. But sources.list isn't a good source of information, you may have changed sources.list after backends file(s) have been generated. How should I know? > Which host is apt-cacher-ng retrying to connect to and failing? Is > this host called "debrep"? If so why is it trying to connect to "debrep" is a "repository", i.e. a common virtual cache path to canalize and/or obfuscate access to mirrors. See file:///usr/share/doc/apt-cacher-ng/html/config-serv.html for details. > "debrep"? If not, why is the name of the unreliable host not given in > the log? Huh? Have you ever looked at log files? $ grep resolving /var/log/apt-cacher-ng/apt-cacher.err Regards, Eduard. -- Intelligenz ist Einsicht und Weite des Bewußtseins, die sich auf alle Gebiete des Lebens erstrecken kann und keineswegs nur auf Beruf und Schule. -- H. Bauer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
