From: Andrey Repin <anrdaemon@yandex.ru>
To: Houder <houder@xs4all.nl>, cygwin@cygwin.com
Subject: Re: Clueless! sshd ONLY fails at system startup (XP/SP3) ...
Date: Thu, 25 May 2017 16:05:00 -0000 [thread overview]
Message-ID: <1362259325.20170525185937@yandex.ru> (raw)
In-Reply-To: <20c9be1102ad4e7590b837c068d3f0ba@xs4all.nl>
Greetings, Houder!
> Hi,
> 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,
Andrey Repin
Thursday, May 25, 2017 18:57:22
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2017-05-25 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 16:05 Houder
2017-05-25 16:05 ` Andrey Repin [this message]
2017-05-26 6:23 ` Houder
2017-05-25 21:36 ` Clueless! sshd ONLY fails at system startup (XP/SP3) ... minor correction Houder
2017-05-26 7:39 ` Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP Houder
2017-05-26 8:05 ` Brian Inglis
2017-05-26 10:28 ` Houder
2017-05-26 15:05 ` cyg Simple
2017-05-26 17:25 ` Houder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1362259325.20170525185937@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=houder@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).