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 B5F3B3858418 for ; Fri, 1 Apr 2022 20:17:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B5F3B3858418 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 10D744010E for ; Fri, 1 Apr 2022 16:17:07 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.jhmg.net 10D744010E Message-ID: Date: Fri, 1 Apr 2022 13:17:07 -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: 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> From: Jim Garrison In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.3 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: Fri, 01 Apr 2022 20:17:10 -0000 On 4/1/2022 2:21 AM, Henry S. Thompson wrote: > Jim Garrison via Cygwin writes: > >> My Cygwin ssh client stopped working... It would successfully connect to >> the remote (Debian) host but then hang without displaying the command >> prompt. See debug output attached, as well as cygcheck output. >> >> I decided to run setup to see if there was a newer version of openssh. >> In preparation for that I always terminate all Cygwin processes because >> they will interfere with the update. I killed the ssh-agent process and >> on a whim decided to try connecting again. This time it worked. >> >> This would seem to indicate something in ssh-agent is interfering with >> the connection. There are no credentials loaded into ssh-agent. > > 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 > what the likely culprits are. > > ht Thanks for confirming that this is a possible issue. I didn't notice if ssh-agent was in a CPU loop, but will take note if/when it happens again. -- Jim Garrison jhg@acm.org