X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=xdaOU+imjF2gGzusRcSKAMvKRdJqT
	qSQt3kto8KD/FGJtvHENZvWrMQG0r4QdZa/sWWvPOCaE6timhz2fsrjFa2cFTFif
	Z7erq+3Mtad8E18G5dt+8wGdiM45x25kLISkA+aZf59gTNVAKytz9LUjTgcIH4mm
	RHLXKjW1ftQnIs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; s=default; bh=Ar7wz7zAxi9paXFXuZMv4LAcQZ0=; b=wER
	QeXDAarY5IUair/gYzH3/i4oGgmQHTzeNp407yrcBWuveaTAnKM7v1vE9vaMmRz4
	HL8DWuPz0T8Xipi0ybKsCvTbfOb6P826GvzIf7fEyFMQOEloB9M4iUCrmm0eJJ6l
	/Rglk69KZSLw7wSF3Iv8US5kUy0v6gsPV7wqErCI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
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
From:	Hiya Z <hiya DOT zyx AT gmail DOT com>
Date:	Thu, 28 Jun 2018 14:31:00 -0700
Message-ID:	<CAFcD33OE_WnzOaHDaYm36wLSzPOOmvXDXuuhM4D7b2PWry+R5A@mail.gmail.com>
Subject:	Re: sshd issues on Windows 10 version 1803
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

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 <corinna-cygwin AT cygwin DOT com
> 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

- Raw text -