From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.jhmg.net (smtp.jhmg.net [45.55.176.36]) by sourceware.org (Postfix) with ESMTPS id C5C263858D37 for ; Sun, 3 Apr 2022 17:15:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C5C263858D37 Received: from [192.168.10.7] (c-73-11-123-33.hsd1.or.comcast.net [73.11.123.33]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.jhmg.net (Postfix) with ESMTPSA id 4997840100 for ; Sun, 3 Apr 2022 13:15:23 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.jhmg.net 4997840100 Message-ID: <04c8f765-6bf6-b8ff-ca94-e88fc21838d2@jhmg.net> Date: Sun, 3 Apr 2022 10:15:23 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.7.0 Reply-To: jhg@acm.org Subject: Re: [cygwin] Re: OpenSSH 8.9p1-1 Connects successfully but then hangs - Killing ssh-agent resolves the issue Content-Language: en-US To: cygwin@cygwin.com References: <3ed89752-9676-a668-f63c-1a9b7662d7b5@jhmg.net> <000401d84750$9147d7b0$b3d78710$@pdinc.us> From: Jim Garrison In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2022 17:15:25 -0000 On 4/3/2022 9:50 AM, Henry S. Thompson wrote: > Jason Pyeron writes: > >>> -----Original Message----- >>> From: Henry S. Thompson >>> Sent: Friday, April 1, 2022 5:21 AM >>> >>> Jim Garrison via Cygwin writes: >>> >>>> My Cygwin ssh client stopped working... It would successfully connect to >>>> ... >>> There are reports out there of ssh-agent getting stuck: just out of >>> curiousity if this happens again, check to see if ssh-agent is using >>> 100% of a CPU. If so then search for "ssh-agent" "100% CPU" to see > >> I did not find much with that search. I found >> https://cygwin.com/pipermail/cygwin/2010-January/183237.html but the >> issue description and resolution was useless. >> >> Do you have certain search results in mind? This happens to me >> several times a month - on multiple systems. Note this started >> within the past 3 years. > > There are three distinct groups of possibly relevant threads, to do > with interactions between ssh-agent and one of > ServerTree [no idea what that is] > GitHub > gnome-keyring-daemon > > Also, if (my own case), I use gpg-agent maskerading as ssh-agent, and > _it_ has the 100% problem sometimes. > > Of course, none of this is relevant if the OP's problem with ssh is > not co-occuring with ssh-agent chewing up an entire processor. The problem has not recurred (yet) so I don't know if ssh-agent was at 100% CPU. All I know at this point is that ssh-agent is *definitely* involved because killing that process restored ssh functionality. I.e. before killing ssh-agent: ssh connects but no prompt is displayed after killing ssh-agent: ssh connects and operates normally -- Jim Garrison