DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=hAvOvVo+5JJu/Wl3hevuAvlSL47+G
	sHeAxO9z/AEH7Zuu8ksuJn6CcLiD89apaObw0CDlDDedEIEeDRp8JLAGEOlZszdN
	TioAWrv3vp0YN4TWPtK6UA0Wp04jdtdvhfpMDr/glSqiFqJep7doAuGHtosRK0Z8
	gd8J83LXjOiauw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Date: Tue, 1 Apr 2014 13:38:46 -0700
Message-ID: <CA+jjjYRFxjg=0EOoygyO_3hcA9U2CkzZQqW6zfn3kvUVO75wVQ@mail.gmail.com>
Subject: sshd buildup of CLOSE_WAIT leading to unable to function
From: Joshua Hudson <joshudson@gmail.com>
To: cygwin <cygwin@cygwin.com>
Content-Type: text/plain; charset=UTF-8

Hi. I'm getting a situation on one machine where sshd will fail to
accept connections in a way that says "connection refused" even though
it is listening. The server shows a large (58) number of connections
in CLOSE_WAIT.

A Google search leads me to
http://www.cygwin.com/ml/cygwin/2010-01/msg01235.html
and eventually to
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q198663
but I don't think that's right. Somebody else managed to this this in 2009
http://www.44342.com/ssh-f1158-t3789-p1.htm


Version:

OpenSSH_6.4p1, OpenSSL 1.0.1e 11 Feb 2013
CYGWIN_NT-6.1 redacted 1.7.25(0.270/5/3) 2013-08-31 20:37 x86_64 Cygwin

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