Re: "500 Can't resolv address for"
Luuk de Boer (luuk_de_boer@pi.net)
Tue, 5 Aug 1997 10:41:10 +1.00
> 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).
I was testing Marc's parallel patch for libwww (version 2.2) and did
have the same problem. Only Marc is using for parallel request
IO::Socket::INET instead of LWP::Socket.
When I request 255 url's 253 urls are going well but the 254 url and
the 255 url is giving me a 500 Can't resolve address back.
That's everytime with all different things.
Everytime it's giving from the 254 url a 500 code.
So here my question ..... does my linux (2.0.30 - redhat 4.2) have
any limit for that sort of things. I looked in IO::Socket and tested
a bit and when the 254's url is requested inet_aton is giving nothing
back instead of the same thing the last 253 requests. So is it
possible that there aren't any free sockets or so or different things
with a limit where inet_aton is depending on.
I am using linux 2.0.30 with perl 5.004 patch 1.
Hope someone can help me find this problem. When I know there is a
limit of sockets then I know the parallel patch won't delete the
sockets and I will take a look at that code but I can't see why it
isn't returning inet_aton ....
Greetz....
Luuk
______________________________________________________________
| Luuk de Boer, luuk@pi.net |
| Handleidingen voor het installeren van Shareware programma's |
| voor Planet Internet: http://www.pi.net/~luuk/ |
|--------------------------------------------------------------|