X-Recipient: archive-cygwin AT delorie DOT com 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:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=lV xi50/3gHv2GgM4kRisrRAAoCkRvGzGxJN/ESAw1RcxpxFVLHLndPZXZ/UIdVQXlh e40jiNUULNQy6EyPjpnog0ZoAoNNIj5x6QWmMwCJ4VRUZ6eyThQQNHgU0llzaKTt EoQ/VbatvI4yeu9DJfCDktJu8b+FYoIHdzPPW0pLc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=z7c+QSme VoGus6eMXhsFRMXW29Y=; b=B286201dwPKf+7nC8GHaxH8aNTirFR2vLCaFygt4 dQBbIzC6+Xv5yiGC6UKihHOvhKqg/yIkiEUp51Le8Z1IrVOXeegu9UJ/ohL0S3Os XVjwL9NxLPIDPpWFEwhA1BqSgRClUrFj6EMl1s9MtWPDsctMfDz94x3NlmsIcnc0 LtY= 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-we0-f180.google.com MIME-Version: 1.0 X-Received: by 10.194.189.116 with SMTP id gh20mr4577060wjc.41.1396973184097; Tue, 08 Apr 2014 09:06:24 -0700 (PDT) In-Reply-To: <CA+jjjYRFxjg=0EOoygyO_3hcA9U2CkzZQqW6zfn3kvUVO75wVQ@mail.gmail.com> References: <CA+jjjYRFxjg=0EOoygyO_3hcA9U2CkzZQqW6zfn3kvUVO75wVQ AT mail DOT gmail DOT com> Date: Tue, 8 Apr 2014 09:06:24 -0700 Message-ID: <CA+jjjYSEmmaevBd6bAotwnzAeqGXt6RXxg6J7ZfhVxWL9qTH0A@mail.gmail.com> Subject: Re: sshd buildup of CLOSE_WAIT leading to unable to function From: Joshua Hudson <joshudson AT gmail DOT com> To: cygwin <cygwin AT cygwin DOT com> Content-Type: text/plain; charset=UTF-8 Sorry took so long to reply. Only reply was set to the mailing list but not to me. > BLODA? No listed BLODA installed. CLOSE_WAIT entries do not appear to build up from normal ssh use via the cygwin ssh client. All CLOSE_WAIT entries show IP addresses not ours. (Port is open on a public IP address. Only private key authentication allowed.) On 4/1/14, Joshua Hudson <joshudson AT gmail DOT com> wrote: > 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