This is the mail archive of the
mailing list for the Cygwin project.
Re: Clueless! sshd ONLY fails at system startup (XP/SP3) ...
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Houder <houder at xs4all dot nl>, cygwin at cygwin dot com
- Date: Thu, 25 May 2017 18:59:37 +0300
- Subject: Re: Clueless! sshd ONLY fails at system startup (XP/SP3) ...
- Authentication-results: sourceware.org; auth=none
- Authentication-results: smtp2m.mail.yandex.net; dkim=pass email@example.com
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
> YES, I know, XP is NOT supported anymore ... However, I started
> out on XP ... and it has sshd running as a Window service,
> installed and configured (as approved by Corinna :-)
> ... some time ago I may have upgraded openssh over there (yes, I
> am now running W7) ... I cannot really remember. Yes, sometimes I
> visit (ssh) the "old station" (XP) for info that I am missing.
> (both machines are behind a firewall - rest assured)
> "Suddenly" (yesterday?) I noticed that the "sshd daemon" fails;
> it is started at system startup (i.e. an automatic service).
> 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 sshad"` ?
> ... tried several things ... in the end, I reinstalled Cygwin +
> openssh (a minimal installation) -- using the time machine.
> However this new, minimal installation of Cywin fails in the exact
> same way!
> Again tried some things ... Finally, I decided to post my problem.
> 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
> Do I interpret this correctly? The child (sshd) fails to "allocate
> stack for the parent (sshd)" ...
> WHY does this only happen at system STARTUP ?????
Any "antivirus" running on that system?
Did you try to fully rebase your installation?
With best regards,
Thursday, May 25, 2017 18:57:22
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple