From: "Wells, Roger K." <ROGER.K.WELLS@leidos.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: EXTERNAL: Re: sshd high cpu load
Date: Fri, 21 May 2021 12:54:33 +0000 [thread overview]
Message-ID: <d1ec09f58b504674bfcbe30563b6ba11@leidos.com> (raw)
In-Reply-To: <18110643390.20210520233304@yandex.ru>
On 5/20/21 4:35 PM, Andrey Repin wrote:
> CAUTION: This email originated from outside of Leidos. Be cautious when clicking or opening content.
>
> Greetings, Wells, Roger K.!
>
>>> On 5/19/2021 12:48 AM, A. Doggy wrote:
>>>>
>>>> I am running cygwin openssh as a windows service. I have been doing
>>>> so for many years with out issue. Recently, I have been running into
>>>> an issue where it maxes out my cpu on any version newer than 8.4p1-1.
>>>> The solution is to downgrade to 8.4p1-1. My server machine is a dell
>>>> t330 running windows 10. I am not a business despite using business
>>>> grade hardware.I have tried both 20h2 and 21h1 but no luck. There are
>>>> no users signed in when the issues occur and occurs within minutes of
>>>> booting up. The only change from the default config is I have it
>>>> running on a nonstandard port. Any advice is welcome as I really
>>>> would like to upgrade to a newer version. Thanks
>> I noticed your initial contact and tried to duplicate what you observed
>> to no avail.
> https://cygwin.com/pipermail/cygwin/2021-April/248299.html
>
>> I set up cygwin openssh as a windows service as you described and also
>> have been doing it this way for many years.
>> sshd.exe doesn't show any cpu load on task manager even after days (yes
>> it still works when I log in from another machine)
>> My system is a Lenovo Thinkpad-x240 running updated W10. Cygwin is at
>> 3.2.0(0.340/5/3)
>> and ssh is at OpenSSH_8.5p1, OpenSSL 1.1.1f 31 Mar 2020.
>> Let me know if you would like me to try something else.
> Connect from remote machine to the usual shell prompt and force kill remote
> ssh process.
> The hung SSH session will cause full core CPU load.
will do & report back
>
>
> --
> With best regards,
> Andrey Repin
> Thursday, May 20, 2021 23:31:39
>
> Sorry for my terrible english...
>
--
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells@leidos.com
next prev parent reply other threads:[~2021-05-21 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 4:48 A. Doggy
2021-05-20 16:02 ` A. Doggy
2021-05-20 16:10 ` [cygwin] " Jason Pyeron
2021-05-20 18:48 ` EXTERNAL: " Wells, Roger K.
2021-05-20 20:33 ` Andrey Repin
2021-05-20 23:12 ` [cygwin] " Jason Pyeron
2021-05-21 12:54 ` Wells, Roger K. [this message]
2021-05-21 1:31 ` A. Doggy
2021-05-22 15:52 ` Andrey Repin
2021-05-26 0:23 ` A. Doggy
2021-05-27 11:51 ` A. Doggy
2021-05-28 23:06 ` A. Doggy
2021-05-28 23:44 ` A. Doggy
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=d1ec09f58b504674bfcbe30563b6ba11@leidos.com \
--to=roger.k.wells@leidos.com \
--cc=cygwin@cygwin.com \
/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).