Comment 4 for bug 33524

Revision history for this message
In , Eduard Bloch (edi-gmx) wrote : Re: Bug#332748: apt-cacher: gets confused after some time, returns error 500

retitle 332748 User::Agent throwing bogus "Bad hostname" errors after a while
reassign 332748 libwww-perl
thanks

Marc Haber schrieb am Sonntag, den 09. Oktober 2005:

> 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.

I am reassigning this report to LWP since it throws those errors and we
cannot see the reason. I don't think this is a fault in apt-cacher code,
because all it does is:

use LWP::User::Agent -> start a daemon -> accept a connection -> fork ->
-> create the LWP::User::Agent object in the child and use it.

The child processes should not have much in common, the bug most come
either from Perl itself or from some internal failure in the LWP modules
in the parent process, since all child processes forked from it after a
certain moment show the same symptoms.

Eduard.
--
Wer wirklich noch einen 4.x-Browser benutzt, dem kann leider nicht mehr
geholfen werden. Die haben soviele Sicherheitsloecher, da koennten wir per
www.linuxtag.org, Exploit und etwas Scriptmagic einen neuen Browser von
Remote installieren.
                                              // Michael Kleinhenz, lt2k-ml