Re: [Bug-wget] wget 1.11.4 hangs on Connecting

[Paul McFerrin]

I thanked the people who decided to participate in my experiment.  As a 
result, the failure was not reproducible. I did however submit this 
problem to the "Bug-wget" mailing list since the code was being blocked 
on a Connection despite the -T 20 option being used.

Paul McFerrin wrote:
> I have a application that periodically polls various existing websites 
> and then alert me if my internet (home ISP) service is interrupted.  
> I'm using wget 1.11.4 (cygwin's distro) to be the work horse.  Wget 
> fails to Connect on a good & known website.  I', using the -T 20 
> option and it appears to just HANG and not timeout.   It fails 
> intermittently and the error messages typically look like this:
>        --2009-02-17 21:36:49--         
> http://home.att.net/~paulmcferrin/index.html
>       Resolving home.att.net... 204.127.208.23
>       Connecting to home.att.net|204.127.208.23|:80...
>                                                                   
>         ^^^
>                                                                      
> -- "Connected" missing
> The failure can occur 4-5 times in a 24-hour period or 100+ times in 
> same period  Besides pinging Worldnet (netscape enterprise 4.x), I'm 
> also pinging my own two Apache 1.x server running on the same PC as 
> the pinging application,  I'm using the following command line for the 
> pings:
>      wget -T 15 --no-dns-cache $DOMAIN -O /dev/null  \
>          2>trace_out_tmp || \
>               (sleep 7 && \
>                      wget -T 15 --no-dns-cache \
>                          $DOMAIN -O /dev/null 2>trace_out_tmp)
> Supplying "--no-dns-cache" has no effect on this problem.
>
> The same PC is also running Firefox all day long and I don't notice 
> any problems with accessing webpages; including the pages being 
> pinged.  When the error log sdoes not show the "Connected" on the 
> connecting line, the process/read hangs and will NOT timeout as 
> specified with the -T option,  Another item to note that it always 
> seems to resolve finding hostname in DNS since it has the site's 
> correct IP address.
>
> On certain days, I can go nearly one whole day without a single 
> failure.  And then there are the other days with failures.   Is this a 
> bug?????
> - Paul