From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: [cygwin] Re: OpenSSH 8.9p1-1 Connects successfully but then hangs - Killing ssh-agent resolves the issue
Date: Sun, 3 Apr 2022 10:15:23 -0700 [thread overview]
Message-ID: <04c8f765-6bf6-b8ff-ca94-e88fc21838d2@jhmg.net> (raw)
In-Reply-To: <f5br16exga2.fsf@ecclerig.inf.ed.ac.uk>
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
next prev parent reply other threads:[~2022-04-03 17:15 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
2022-04-03 11:47 ` [cygwin] " Jason Pyeron
2022-04-03 16:50 ` Henry S. Thompson
2022-04-03 17:15 ` Jim Garrison [this message]
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=04c8f765-6bf6-b8ff-ca94-e88fc21838d2@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).