Re: "500 Can't resolv address for"

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Gisle Aas: "Re: LWP::Simple and shtml targets"
• Previous message: Gisle Aas: "Re: Problem: HTTP::Message calls to HTTP::Headers"
• In reply to: Hans de Graaff: "Re: "500 Can't resolv address for""
• Next in thread: Luuk de Boer: "Re: "500 Can't resolv address for""

Hans de Graaff <J.J.deGraaff@twi.tudelft.nl> writes:

> Scott Kaplan <scott@sflegal.net> writes:
> 
> > I noticed a similar intermittent problem when I was doing the intial
> > testing running Checkbot from the command line.  When I was running
> > Checkbot manually, I noticed it would run about a third of the way
> > through the site, then every link would generate the error 500.
> 
> To further clarify things, it seems that at a certain point LWP starts 
> to return a 500 error for every link, seemingly regardless of whether
> there can be resolved or not. This seems to suggest some internal
> state hangs around. I also seem to rememer the 500 errors coming very
> quickly, instead of timing out again and again as one would expect.

I have seen this with another link checker I wrote.  I suspect that it
has something to do with how (badly) perl handles signals and the fact
that we use alarm for timeouts.  Wishing I had time to do the
event-loop rewrite of lwp (and that perl had an event-loop).

-- 
Gisle Aas <aas@sn.no>

• Next message: Gisle Aas: "Re: LWP::Simple and shtml targets"
• Previous message: Gisle Aas: "Re: Problem: HTTP::Message calls to HTTP::Headers"
• In reply to: Hans de Graaff: "Re: "500 Can't resolv address for""
• Next in thread: Luuk de Boer: "Re: "500 Can't resolv address for""