public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Apache Fork Errors - Found on Windows Server 2019
Date: Thu, 14 Oct 2021 22:05:51 -0700	[thread overview]
Message-ID: <e9433bb2-2965-f167-d555-07bda7df260a@maxrnd.com> (raw)
In-Reply-To: <CAK0ZC5W61MjdXxLwAaeRHK4u9ovW0BsLZ3RuZT+DPvcgte+X-g@mail.gmail.com>

Hi,

OwN-3m-All via Cygwin wrote:
> Hi All,
> 
> I can't seem to get apache via cygwin to work on Windows Server 2019.
> 
> Here is my error log:
> 
>        0 [main] httpd 1360 child_info_fork::abort:
> \??\C:\OGP64\bin\cygharfbuzz-0.dll: Loaded to different address:
> parent(0x3FAF60000) != child(0xCD0000)
> [Thu Oct 14 20:21:24.306514 2021] [mpm_prefork:error] [pid 3203]
> (11)Resource temporarily unavailable: AH00159: fork: Unable to fork new
> process
> [Thu Oct 14 20:21:32.643467 2021] [mpm_prefork:notice] [pid 3203] AH00163:
> Apache/2.4.39 (Unix) PHP/7.3.7 configured -- resuming normal operations
> [Thu Oct 14 20:21:32.643698 2021] [core:notice] [pid 3203] AH00094: Command
> line: '/usr/sbin/httpd -D NO_DETACH'
> [Thu Oct 14 20:21:32.644325 2021] [mpm_prefork:notice] [pid 3203] AH00169:
> caught SIGTERM, shutting down
[etc etc etc]
> 
> I issued the "rebase-trigger fullrebase" command and ran the cygwin setup
> for it to rebase.  I rebooted the server, and that didn't make a difference.

Makes sense to have tried that; thanks for reporting outcome.

> Any idea why this is happening or how to fix it?

Been a long time since I've run Apache and that wasn't even on Cygwin, but...
Apache had/has two run modes, pre-forking and threaded.  It appears you're running 
it in pre-forking mode.  Try running it in threaded mode.  This might be 
controlled by httpd.conf or some other Apache config file.

If somebody else on the list is successfully running Apache on Cygwin, maybe they 
can chime in on which mode they're using.
HTH,

..mark

  reply	other threads:[~2021-10-15  5:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  3:38 OwN-3m-All
2021-10-15  5:05 ` Mark Geisert [this message]
2021-10-15 17:25   ` OwN-3m-All
2021-10-15 18:55 ` Achim Gratz
2021-10-15 19:12   ` OwN-3m-All
2021-10-15 19:35     ` OwN-3m-All
2021-10-15 20:04       ` OwN-3m-All
2021-10-15 20:25         ` Ken Brown
2021-10-17  1:49           ` OwN-3m-All
2021-10-17 15:54             ` Ken Brown
2021-10-17 16:40               ` Brian Inglis
2021-10-18 20:43               ` OwN-3m-All
2021-10-18 21:25                 ` Ken Brown
2021-10-19  1:43                   ` OwN-3m-All
2021-10-19 20:07                     ` Ken Brown
2021-10-20  3:22                       ` OwN-3m-All
2021-10-17  9:40 ` 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=e9433bb2-2965-f167-d555-07bda7df260a@maxrnd.com \
    --to=mark@maxrnd.com \
    --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).