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
--
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
