From: "Michael Lemke" <lemkemch@t-online.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Apache rebase trouble
Date: Sun, 21 May 2017 20:22:00 -0000 [thread overview]
Message-ID: <op.y0lt4cpgaqc5s6@orion.localdomain> (raw)
For some reason I keep getting these problems in my apache installation that used to run just fine:
2 [main] httpd 1624 child_info_fork::abort: unable to remap zip.dll to same address as parent (0x13B0000) - try running rebaseall
[Sun May 21 17:54:00.047667 2017] [mpm_prefork:error] [pid 5984] (11)Resource temporarily unavailable: AH00159: fork: Unable to fork new process
2 [main] httpd 5272 child_info_fork::abort: unable to remap bz2.dll to same address as parent (0xAE0000) - try running rebaseall
[Sun May 21 17:54:10.094156 2017] [mpm_prefork:error] [pid 5984] (11)Resource temporarily unavailable: AH00159: fork: Unable to fork new process
I tried this several times:
rebase-trigger full
followed by running setup and making sure no cygwin process was running. I could see in process explorer that rebase was running but it didn't help.
What can I try to make my apache httpd installation work again? Cygwin on XP:
orion> uname -a
CYGWIN_NT-5.1 orion 2.5.2(0.297/5/3) 2016-06-23 14:27 i686 Cygwin
--
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 reply other threads:[~2017-05-21 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 20:22 Michael Lemke [this message]
2017-05-21 20:45 ` Marco Atzeri
2017-05-23 15:25 ` Houder
2017-05-23 0:29 Michael Lemke
2017-05-23 19:51 ` Achim Gratz
2017-05-23 20:05 ` Michael Lemke
2017-05-23 20:17 ` Achim Gratz
2017-05-23 21:02 ` Michael Lemke
2017-05-23 23:56 ` Michael Lemke
2017-05-24 2:53 ` Michael Enright
2017-05-25 15:29 ` Michael Lemke
2017-05-24 10:14 ` Andrey Repin
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=op.y0lt4cpgaqc5s6@orion.localdomain \
--to=lemkemch@t-online.de \
--cc=cygwin@cygwin.com \
/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).