X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 20 Jan 2012 14:31:17 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ssh/scp sometimes unable to connect
Message-ID: <20120120133117.GS22712@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4F188BC7 DOT 5020305 AT cs DOT utoronto DOT ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F188BC7.5020305@cs.utoronto.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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