From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by sourceware.org (Postfix) with ESMTPS id B010D3858025 for ; Thu, 27 May 2021 11:51:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B010D3858025 Received: by mail-ej1-x629.google.com with SMTP id l3so1654966ejc.4 for ; Thu, 27 May 2021 04:51:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=m8NzWKMdFlRiCQ5w7ufhSBsx8dE8TsCDfcAAimzuOKQ=; b=jgW1ssjLV3J1S7t/YWV7FhtljlLAZgW49nnGy3dk94lClxjFiWpfSrgBEHCO0pTEXc ycwXXmZozAoMqUB0eQJTFFIX2FIanG2Uf8oNVbCD/VcP6TYg9Iigw36l9SNiLAqm2WMi Ul6vajDr7xg6+3YQOLQ6AvO6Af582CuTN6LJtZyIb+AaS8gcdFfWQe65YSEjqvtOvYmH +ynliwa+g8lbSn6VsPg9Xabd58GrnUp126gVnr7gDfefe4ZqDHMBkVIB2EyLHSPVPgGW rLJlTBKaXzWb1NHti+VWugPpW1BrjCjj2kBAYLeFnmOsrtH24FL3jGtIvkVJfNf+TgPp pp4Q== X-Gm-Message-State: AOAM532dr0fXFqINLDM6e5wGTCt8XkBrO3MfSN88BYPl/nTZ7FJYB4LT rhSMJ3rLWhKWetbP6sMGAxwghg5XzTc= X-Google-Smtp-Source: ABdhPJxuFrt7maAvlVTasTubJqqs7kizH7vF3qyoDqxLy08HHG94A9VhRS5n/eNl5DBYOwcunJmmDQ== X-Received: by 2002:a17:906:b756:: with SMTP id fx22mr3348346ejb.224.1622116302469; Thu, 27 May 2021 04:51:42 -0700 (PDT) Received: from [192.168.1.19] (pool-108-27-17-105.nycmny.fios.verizon.net. [108.27.17.105]) by smtp.gmail.com with ESMTPSA id c7sm930995ede.37.2021.05.27.04.51.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 May 2021 04:51:41 -0700 (PDT) Subject: Re: sshd high cpu load From: "A. Doggy" To: cygwin@cygwin.com References: <7bd9875a-691e-95fe-77ea-4c8ccd98a46d@gmail.com> <43f334cb-2da2-c9d7-be73-94f311ec63b4@gmail.com> <908a746f-dd54-775b-7dfd-27e453d1a6da@gmail.com> Message-ID: Date: Thu, 27 May 2021 07:51:40 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: <908a746f-dd54-775b-7dfd-27e453d1a6da@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2021 11:51:45 -0000 On 5/25/2021 8:23 PM, A. Doggy wrote: > > On 5/20/2021 9:31 PM, A. Doggy wrote: >> To cygwin. >> >> >> A Little more info: I actually have 1 client that connects regularly >> to the server. That client uses a program called goodsync. When I >> block goodsync from connecting, the problem goes away and I only have >> 1 sshd.exe process running. When I unblock goodsync, I have multiple >> sshd.exe processes running and my cpu gets maxed out. Please test it >> like this. Thanks. >> >> On 5/20/2021 12:02 PM, A. Doggy wrote: >>> Anyone? >>> >>> On 5/19/2021 12:48 AM, A. Doggy wrote: >>>> To Cygwin, >>>> >>>> >>>> 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 >>>> > > > > To Cygwin, > > > I remember seeing someone was going to work on this on Sunday. I am > checking if this is resolved for other users as I do not want to > update and be stuck. Thanks. > bump To Cygwin, I remember seeing someone was going to work on this on Sunday. I am checking if this is resolved for other users as I do not want to update and be stuck. Thanks.