From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: "Jason Pyeron" <jpyeron@pdinc.us>
Cc: <cygwin@cygwin.com>
Subject: Re: [cygwin] Re: OpenSSH 8.9p1-1 Connects successfully but then hangs - Killing ssh-agent resolves the issue
Date: Sun, 03 Apr 2022 17:50:29 +0100 [thread overview]
Message-ID: <f5br16exga2.fsf@ecclerig.inf.ed.ac.uk> (raw)
In-Reply-To: <000401d84750$9147d7b0$b3d78710$@pdinc.us> (Jason Pyeron's message of "Sun\, 3 Apr 2022 07\:47\:16 -0400")
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.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
next prev parent reply other threads:[~2022-04-03 16:50 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 [this message]
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=f5br16exga2.fsf@ecclerig.inf.ed.ac.uk \
--to=ht@inf.ed.ac.uk \
--cc=cygwin@cygwin.com \
--cc=jpyeron@pdinc.us \
/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).