X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.3 required=5.0 tests=AWL,BAYES_50,J_CHICKENPOX_31,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<499B9DBB.5030107@columbus.rr.com>
Date:	Wed, 18 Feb 2009 00:33:47 -0500
From:	Paul McFerrin <pmcferrin AT columbus DOT rr DOT com>
Reply-To:	pmcferrin AT columbus DOT rr DOT com
User-Agent:	Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	wget 1.11.4 intermittently fails to connect
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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 and ping xxx.x to be the work horse.  Wget fails to 
Connect on a good & known website.  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 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.

If I can get a couple of people to issue the above commands from their 
PC to see if it is reproducible from different sites?  For $DOMAINS, use:
           http://home.att.net/~paulmcferrin/index.html     OR
           http://genealogy.mcferrin.org/index.html     OR
           http://pmcferrin.homedns.org/index.html
and report back (use p_e_mcferrin AT  yahoo.com) your findings.  I don't 
seem to have any any problems doing "ping's"

                                    Thanks in advanced, Paul

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -