X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org A3567398B42F
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1621601677;
	bh=67x+0KcQ5rQ6xU/EY0RJmD1uj9CyvSkrSCaXz9z/oFM=;
	h=To:Subject:Date:References:List-Id:List-Unsubscribe:List-Archive:
	List-Post:List-Help:List-Subscribe:From:Reply-To:From;
	b=v8O26xEbDWTsdyf72ORjDZncdjS7wV5k1oV1vrATZMzFDKHHULBA9DLwq0uKXQ12u
	6iRiLZ2F9YCvKoO0TFRCOuSVz1Vsl9goIdb2HoJVNecHyudUBdQOe+R7Wvxozo5Vgq
	f4HhPXNFjbIZhvq99SqLbgeabSt0Z32SUhdYgSTA=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 537B63848039
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Re: EXTERNAL: Re: sshd high cpu load
Thread-Topic:	EXTERNAL: Re: sshd high cpu load
Thread-Index:	AQHXTkBytY/xoFrvLEmbO4a5XsGh5g==
Date:	Fri, 21 May 2021 12:54:33 +0000
Message-ID:	<d1ec09f58b504674bfcbe30563b6ba11@leidos.com>
References:	<cda40b2d-e10b-220c-ec08-ac3a1c48b36f AT gmail DOT com>
	<7bd9875a-691e-95fe-77ea-4c8ccd98a46d AT gmail DOT com>
	<42988d13958e4b298f649190c800bcf8 AT leidos DOT com>
	<18110643390 DOT 20210520233304 AT yandex DOT ru>
Accept-Language:	en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip:	[149.8.144.235]
MIME-Version:	1.0
X-Proofpoint-ORIG-GUID:	Jw9VBkclZ2Q1CbEjExaGtx0gLzjwGS7v
X-Proofpoint-GUID:	Jw9VBkclZ2Q1CbEjExaGtx0gLzjwGS7v
X-Proofpoint-Spam-Details:	rule=notspam policy=outbound score=0 clxscore=1015
	priorityscore=1501
	adultscore=0 mlxscore=0 malwarescore=0 phishscore=0 lowpriorityscore=0
	bulkscore=0 suspectscore=0 spamscore=0 impostorscore=0 mlxlogscore=870
	classifier=spam adjust=-150 reason=mlx scancount=1
	engine=8.12.0-2104190000 definitions=main-2105210076
X-Spam-Status:	No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	"Wells, Roger K. via Cygwin" <cygwin AT cygwin DOT com>
Reply-To:	"Wells, Roger K." <ROGER DOT K DOT WELLS AT leidos DOT com>
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

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 DOT k DOT wells AT leidos DOT com


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

- Raw text -