X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0FC33383942B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1648844259; bh=JxbWDGZ6YLMMlVR2olMMmIC0Jop9ZNCXCB0IwQYtG3g=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=jIxTfEN6A4LIEvqWPclVzukF7bN3GyNUzuzAELIlOtkIkEszHU9Sglj6g+COdXsLa GkzqMicYV31kc3BXZRsQsAOGF+AJJm3DEdNkixFRhDBHRprKSmAalMs6/a98GBrcIc trZs2wsSZqDj8B3f+EQCX1tGFtXeaxWTiw3D5UZk= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B5F3B3858418 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 Subject: Re: OpenSSH 8.9p1-1 Connects successfully but then hangs - Killing ssh-agent resolves the issue Content-Language: en-US To: cygwin AT cygwin DOT com References: <3ed89752-9676-a668-f63c-1a9b7662d7b5 AT jhmg DOT net> In-Reply-To: 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 AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Jim Garrison via Cygwin Reply-To: jhg AT acm DOT org Cc: Jim Garrison Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Cygwin" 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 AT acm DOT org -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple