On Sun, Oct 09, 2005 at 05:33:47PM +0200, Eduard Bloch wrote: > > See attached log of a failed aptitude update run, and the working one > > after restarting apt-cacher (2400 lines). > > I do not understand where it comes from. Following this report, the > errors are reported by the http client module, the fetcher part. But it > does not make any sense. The HTTP user agent object is created > separated in every forked process. > > Further, I think there are bad things happening with your connection, > see > Sat Oct 8 13:01:18 2005|127.0.0.1|debug: Header sent: 500 (Internal Server > Error) Can't connect to debian.debian.zugschlus.de:80 (Bad hostname > 'debian.debian.zugschlus.de') > > So where does the DNS error come from? Broken nscd or something like > that? libc6 upgrade without restartint services?
Today's failure happened out of the blue when no administration work was done - none on the system running apt-cacher, and none on the system running the full service resolver for the apt-cacher box. The connection and DNS servers were fine, shown by mail services processing incoming messages without delay. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
