X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,TW_FC X-Spam-Check-By: sourceware.org Message-ID: <4F198D6D.4030303@cs.utoronto.ca> Date: Fri, 20 Jan 2012 10:51:09 -0500 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "cygwin AT cygwin DOT com" Subject: Re: ssh/scp sometimes unable to connect References: <4F188BC7 DOT 5020305 AT cs DOT utoronto DOT ca> <20120120133117 DOT GS22712 AT calimero DOT vinschen DOT de> In-Reply-To: <20120120133117.GS22712@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 20/01/2012 8:31 AM, Corinna Vinschen wrote: > On Jan 19 16:31, Ryan Johnson wrote: >> Hi all, I just re-ran setup.exe yesterday and now ssh behaves >> erratically, often timing out instead of asking for a password: >>> $ ssh cs.utoroto.ca ssh: connect to host cs.utoroto.ca port 22: >>> Connection timed out >> I rebased my system after the update and replaced the 13 Nov snapshot >> I've been using with the one from 11 Jan, but the problem persists. >> This doesn't seem to be fork-related in any obvious way: ssh runs but >> then times out on an fcntl syscall (see attached strace.out). >> Normally I'd blame the network or the host, but sysadmins for the >> machine are unaware of anything that might cause the problem; I can >> maintain an open ssh connection to that host (cpu and memory usage >> there are both low) and can connect to it from other terminals >> windows during the failing attempt, which suggests the problem is on >> my side of the network. Even more strangely, changing things (ssh >> instead of scp, different user name, different host alias) makes it >> work or not (and, of course, sometimes it just works). Running strace >> or not doesn't seem to make a difference, though. > There's nothing weird in the strace. Your connect call gets a WinSock > error 10060, WSAETIMEDOUT, that's all. There were no changes to the > connect call since May 2011. At this point, not even the new OpenSSL > 0.9.8t should be involved. Grr. I tried to send a reply yesterday, but apparently the list bounced it due to mime type text/html (why , Thunderbird, why???). It was PEBCAK -- typing 'utoroto.ca' rather than 'utoronto.ca' -- compounded by the fact that ssh apparently reports DNS failures as if they were merely connection timeouts. Sorry for the false alarm. Ryan -- 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