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:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=XjKLHH3VWmY4EgothEBM
	57zGTR7Jtndn88BQF8CxLN3PO5rymGUFNEBX8kloFRYnMFkz/btKOnXU8X3yKe2g
	mEM4ovcyDew3Iy0NMzbRRJWDRTMeAMqtAr54W34rF7pw/RrULrm8XxZ+/KZ5q7rv
	Dco2TuY4TfGo+omr4UbD+x4=
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:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; s=default; bh=iZ6fXZ7L6/PC/Sm44DVPmslXBE
	w=; b=Wt09tXGh9QLIGYn252lEwx0mh8YpAmZ84MNqvWsBCXPay7RAYWRtNB4xT8
	fQ0ul9+10x6tDHHkZJhqPU7PLOMqSsjdtQmqV+kLffK/t5i7geIC7Cu7LwasNJ6Z
	opZPokUhRTlvNiE9Z4vKhpj9IuxNcw015VHVII5o5ORGGaKWQ=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=wiser, H*F:D*nl, died, antivirus
X-HELO:	lb2-smtp-cloud2.xs4all.net
MIME-Version:	1.0
Date:	Fri, 26 May 2017 07:33:46 +0200
From:	Houder <houder AT xs4all DOT nl>
To:	cygwin AT cygwin DOT com
Subject:	Re: Clueless! sshd ONLY fails at system startup (XP/SP3) ...
In-Reply-To:	<1362259325.20170525185937@yandex.ru>
References:	<20c9be1102ad4e7590b837c068d3f0ba AT xs4all DOT nl> <1362259325 DOT 20170525185937 AT yandex DOT ru>
Message-ID:	<bee7f844a577639ea4b2da1d865b814e@xs4all.nl>
X-Sender:	houder AT xs4all DOT nl
User-Agent:	XS4ALL Webmail
X-IsSubscribed:	yes

On 2017-05-25 17:59, Andrey Repin wrote:

Hi Andrey,

[snip]
>> When the service is restarted after system startup, i.c.
> 
>>      cygrunsrv -E sshd; cygrunsrv -S sshd
> 
>> it then works flawlessly (which amazes me, given the error in
>> the sshd.log)
> 
> What if you `net start "Cygwin sshd"` ?

You mean after system startup? It tells me that "the requested service
has already been started." ... and sshd still fails when I approach it
again.
(yes, "net stop ...", followed by "net start ..." again does the trick)

[snip]
>> Any suggestions? (Yes, XP has F-Secure as anti-virus)
> 
>> The message in the sshd.log:
> 
>> Server listening on 0.0.0.0 port <X>.^M # X = some port, but not 22
>>        1 [main] sshd 3152 E:\Cygwin25\usr\sbin\sshd.exe: *** fatal 
>> error
>> in forked process - fork: can't reserve memory for parent stack 
>> 0x30000
>> - 0x230000, (child has 0x40000 - 0x240000), Win32 error 487
>>   395874 [main] sshd 3152 cygwin_exception::open_stackdumpfile: 
>> Dumping
>> stack trace to sshd.exe.stackdump
>>        3 [main] sshd 536 fork: child -1 - forked process 3152 died
>> unexpectedly, retry 0, exit code 0x100, errno 11
>> fork: Resource temporarily unavailable^M

[snip]
> Any "antivirus" running on that system?

Yes ... as I wrote in the original post "F-Secure" has been installed, 
and
yes, it may be the culprit ... (would have to UNinstall it, cannot 
switch
it off temporarily).

> Did you try to fully rebase your installation?

I did ... as instructed in /usr/share/doc/Cygwin/_autorebase.README

  - rebase-trigger fullrebase
  - shut down "Cygwin" (incuding: cygrunsrv -E sshd)
  - execute setup ...

It did not help. But read the error report in the sshd.log again: it is
not the "classical dll clash" (description by Michael Lemke :-), it is
"something else" (related to the "lockstep" in which parent and child 
are
forced by the cygwin dll when the fork syscall takes places, and yes, in
those circumstance a dll clash may occur if the Cygwin dlls have not 
been
properly rebased).

As rebasing did not help, I tried some other things, but then decided,
it would be far wiser to install the last valid version of Cygwin.

However the result was the same ...

Subsequently tried the peflags command ... reconfigured openssh in a
different way (using cyg_server as the privileged account - although not
required in XP)

Did some things (that I cannot really remember now). Finally I decided I
did not have a clue of what was going on (and of what I was doing).

That is why I decided to post my problem. I am clueless. More so, as I
can make sshd work by just restarting it ...

Regards,

Henri

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