From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: OpenSSH 8.9p1-1 Connects successfully but then hangs - Killing ssh-agent resolves the issue
Date: Fri, 1 Apr 2022 13:17:07 -0700 [thread overview]
Message-ID: <a987359e-2648-9531-bcab-87f76e694d5a@jhmg.net> (raw)
In-Reply-To: <f5b7d892m7j.fsf@ecclerig.inf.ed.ac.uk>
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
next prev parent reply other threads:[~2022-04-01 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 20:31 Jim Garrison
2022-04-01 9:21 ` Henry S. Thompson
2022-04-01 20:17 ` Jim Garrison [this message]
2022-04-03 11:47 ` [cygwin] " Jason Pyeron
2022-04-03 16:50 ` Henry S. Thompson
2022-04-03 17:15 ` Jim Garrison
2022-04-04 7:25 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a987359e-2648-9531-bcab-87f76e694d5a@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).