From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72707 invoked by alias); 15 Sep 2019 07:07:45 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 72699 invoked by uid 89); 15 Sep 2019 07:07:45 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=4.5 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,FREEMAIL_FROM,GARBLED_BODY,KAM_BADIPHTTP,KAM_SHORT,NUMERIC_HTTP_ADDR,RCVD_IN_DNSWL_NONE,SPF_PASS,WEIRD_PORT autolearn=no version=3.3.1 spammy==d0=b5=d1, rogue, Lee, basin?= X-HELO: mail-lf1-f67.google.com Received: from mail-lf1-f67.google.com (HELO mail-lf1-f67.google.com) (209.85.167.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 15 Sep 2019 07:07:44 +0000 Received: by mail-lf1-f67.google.com with SMTP id w67so25017386lff.4 for ; Sun, 15 Sep 2019 00:07:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=yTDVS9lQJd4cFWqsB9PuIyX3znY+Wi4nwi9N9GEgEMk=; b=t61SCeBgcv77swrII7L0sJkr9jiznFsmwz+dtgxhebib2VVGG0o5AlbKnicGFGRybX nv/RaOVKq7G85bIVP0NWKazcb/rPUZsTXNAsyEpD67njN6Ws1ZjOWw9kxGtOPFNXk0Jt eWY7bsrhY4XnpTc1NIerWcPJDvRuCBj70jtEqxfm11cBwNkckjbQzGEnFMzWiDdCwQYB 24iVynXscBJ+ja7rQxHGd9OXPyMHA/6BA2ughE6j10rgZFDRzDy03xmVBcrcWJ7JFTo6 r6gWpi8iAom1OiTKqr6b3PHtmiWiIEj2XxV+mRKJCAHdDSNvAy9aqPsfoNWp1tYcSFFA oF3w== Return-Path: Received: from [10.190.12.43] (nat-0-0.nsk.sibset.net. [5.44.169.210]) by smtp.googlemail.com with ESMTPSA id s21sm7468994ljj.22.2019.09.15.00.07.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Sep 2019 00:07:41 -0700 (PDT) Subject: Re: Something makes curl hang for 5 minutes after connection refused To: cygwin@cygwin.com References: <20181201095124.GM30649@calimero.vinschen.de> From: Basin Ilya Message-ID: <8621444e-d644-7197-62c7-f3b10a2fb02e@gmail.com> Date: Sun, 15 Sep 2019 10:13:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20181201095124.GM30649@calimero.vinschen.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00178.txt.bz2 Hi. Any update on this? 01.12.2018 12:51, Corinna Vinschen пишет: > On Nov 30 20:42, Brian Inglis wrote: >> On 2018-11-30 12:49, Lee wrote: >>> On 11/30/18, Basin Ilya wrote: >>>> Hi. >>>> >>>> Recently I noticed that `curl` does not fail immediately after connection >>>> refused, but waits for 5 minutes. >>>> >>>> This only happens on my machine and only with the `Cygwin` version of >>>> `curl`. The mingw version is unaffected. >>>> I tried downgrading curl, but it didn't help. I thought there's a rogue >>>> setting in `/etc` or in home or maybe some environment variable, but I >>>> couldn't find it. >>>> >>>> basin@BASIN /cygdrive/c/Users/basin >>>> $ >/dev/null /usr/bin/curl -v http://127.0.0.1:2/ >>>> * STATE: INIT => CONNECT handle 0x80048658; line 1404 (connection >>>> #-5000) >>>> * Added connection 0. The cache now contains 1 members >>>> * Trying 127.0.0.1... >>>> * TCP_NODELAY set >>>> * STATE: CONNECT => WAITCONNECT handle 0x80048658; line 1456 (connection >>>> #0) >>> <.. snip ..> >>>> curl: (28) Connection timed out after 300145 milliseconds >>>> >>>> basin@BASIN /cygdrive/c/Users/basin >>>> $ /usr/bin/curl --version >>>> curl 7.59.0 (i686-pc-cygwin) libcurl/7.59.0 OpenSSL/1.0.2p zlib/1.2.11 >>>> libidn2/2.0.4 libpsl/0.18.0 (+libidn2/2.0.2) libssh2/1.7.0 nghttp2/1.31.0 >>> >>>> Can someone try to reproduce it? >>> >>> I get the same behavior: >>> $ /usr/bin/curl -v http://127.0.0.1:2/ >>> * STATE: INIT => CONNECT handle 0x600057ad0; line 1404 (connection #-5000) >>> * Added connection 0. The cache now contains 1 members >>> * Trying 127.0.0.1... >>> * TCP_NODELAY set >>> * STATE: CONNECT => WAITCONNECT handle 0x600057ad0; line 1456 (connection #0) >>> * Connection timed out after 300324 milliseconds >>> * multi_done >>> * stopped the pause stream! >>> * Closing connection 0 >>> * The cache now contains 0 members >>> curl: (28) Connection timed out after 300324 milliseconds >>> >>> $ /usr/bin/curl --version >>> curl 7.59.0 (x86_64-unknown-cygwin) libcurl/7.59.0 OpenSSL/1.0.2p >>> zlib/1.2.11 libidn2/2.0.4 libpsl/0.18.0 (+libidn2/2.0.2) libssh2/1.7.0 >>> nghttp2/1.31.0 >>> >>> >>> I also get an almost immediate 'failed to connect' notice on windows: >>> C:\>C:\UTIL\curl\curl.exe -v http://127.0.0.1:2/ >>> * Trying 127.0.0.1... >>> * TCP_NODELAY set >>> * connect to 127.0.0.1 port 2 failed: Connection refused >>> * Failed to connect to 127.0.0.1 port 2: Connection refused >>> * Closing connection 0 >>> curl: (7) Failed to connect to 127.0.0.1 port 2: Connection refused >>> >>> with either version of curl: >>> C:\>where curl >>> C:\UTIL\curl\curl.exe >>> C:\Windows\System32\curl.exe >> >> Ditto all the way! >> >> Could this be caused by network speed improvements made to Cygwin a while back? >> Or were those patches never sent/received/applied from Daniel Havey (MS Windows >> Program Manager for Transports and IP)? > > Somebody may want to bisect this... > > > Corinna > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple