From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120205 invoked by alias); 28 Jun 2018 21:31:16 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 120058 invoked by uid 89); 28 Jun 2018 21:31:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=pm, 7000, mails, observe X-HELO: mail-ed1-f45.google.com Received: from mail-ed1-f45.google.com (HELO mail-ed1-f45.google.com) (209.85.208.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Jun 2018 21:31:02 +0000 Received: by mail-ed1-f45.google.com with SMTP id g12-v6so6020660edi.9 for ; Thu, 28 Jun 2018 14:31:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=yPpNLiIXX50HtYHHXszDvmt+2r6EXXTj4DuYMabJFgU=; b=YoqanANkprXfQOtCyACfFZUjlXLDiuzx3aBCyx3ZaNxP4R7rhatWZ+E7Dc2RFx3DvS kRTQrQvTWBb2Xnv+V9SPBybugRjXp1Q0g52+v4MNElgtQAyPnoaWSGF1agH5x/YVYKZW VTHss7VB2yeKLH/WQHYs5g6tmoej2/+P6qG0tB6ESsiOlnmK/sw0hdb7mlHJrO6OSKuw Kn+xsWPU7ihQndf1Jkh/Wokb+kiqo1H/pUtc9YJG3I+EEpOaKC911f8Z7atOxGHltRX5 LnOfPk/t2fHMPLy6baBdQ9tVNmVS386r7GRvoq8P54uOQFlYXH728xolzzSEzZZVBQZt z+yw== MIME-Version: 1.0 Received: by 2002:a50:c385:0:0:0:0:0 with HTTP; Thu, 28 Jun 2018 14:31:00 -0700 (PDT) From: Hiya Z Date: Fri, 29 Jun 2018 06:20:00 -0000 Message-ID: Subject: Re: sshd issues on Windows 10 version 1803 To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00312.txt.bz2 Upon upgrading another 1709 node (with working Cygwin sshd), the 1803 update clobbered the sshd service registry tree. The older Cygwin sshd key was deleted and a new sshd service got created pointing to %SystemRoot%\System32\OpenSSH\sshd.exe. This is different from what I observed on the 1st node that I upgraded a few weeks ago (wherein the Cygwin sshd registry tree was left intact). I deleted the sshd service, rerun ssh-host-config, and am back to random failed auto-restarts of sshd. I think there is a myriad of issues here, the least of which is MS hijacking the "sshd" service name. As a minimum, the default 'service_name' in ssh-host-config should be changed to not conflict with "sshd". Maybe ssh-host-config should also consider deleting any pre-existing "sshd" service and then recreate a new one. The FAQ may require some mention as well. I got another hit of this conflict on the web at https://gist.github.com/roxlu/5038729 (last few comments). Thanks. On Tue, Jun 26, 2018 at 1:16 AM, Corinna Vinschen wrote: > On Jun 25 11:59, Hiya Z wrote: > > >Btw., I can't reproduce this problem. Cygwin's sshd service always > > >starts for me at boottime as expected. > > > > >Did you check if the log file in /var/log contains any more info? > > > > I see nothing in /var/log/sshd.log. Windows event log shows following > > errors: > > > > -- > > Error 6/20/2018 3:45:19 PM Service Control Manager > > 7009 None > > A timeout was reached (30000 milliseconds) while waiting for the sshd > > service to connect. > > > > Error 6/20/2018 3:45:19 PM Service Control Manager > > 7000 None > > The sshd service failed to start due to the following error: > > The service did not respond to the start or control request in a timely > > fashion. > > -- > > > > Another odd behavior that I observe is that after a reboot, starting a > > Cygwin64 terminal (first time) takes a long time. Launching subsequent > > mintty terminals is quick as it should be. Could it be that sshd startup > > upon reboot is hitting the same delay as the 1st mintty? > > > > Will try removing %SystemRoot%\System32\OpenSSH from the PATH to see if > it > > improves things. > > I didn't remove it and it works fine for me. The OpenSSH path is > pretty late in $PATH and should not affect starting with cygrunsrv > because it prepends /bin to $PATH before running the service... > unless you used the -e option to cygrunsrv to infuse your own $PATH. > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Maintainer cygwin AT cygwin DOT com > Red Hat > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple