public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <Dominic.R.Jones@faa.gov>
To: <cygwin@cygwin.com>
Subject: httpd-2.4.23 notice "No slotmem from mod_heartmonitor"
Date: Mon, 25 Jul 2016 23:14:00 -0000	[thread overview]
Message-ID: <9820E0FA51BA9E488013F2BC442C0A6D63E816@006FCH1MPN2-072.006f.mgd2.msft.net> (raw)

After obtaining the upgrade of the httpd package from 2.4.22 to 2.4.23, I received the following error on attempted startup:

    [Mon Jul 25 08:22:26.529504 2016] [proxy_balancer:emerg] [pid 1234] AH01177: Failed to lookup provider 'shm' for 'slotmem': is 
    mod_slotmem_shm loaded??

Activating mod_slotmem_shm (as a shared module) resolved this issue and allowed httpd to start.  However, httpd now produces the following notice on (successful) startup:

    [Mon Jul 25 09:27:40.718810 2016] [lbmethod_heartbeat:notice] [pid 2345] AH02282: No slotmem from mod_heartmonitor

I'm wondering if there changes to the static modules included in the new version's package.  The changelog for httpd itself didn't suggest any changes between these two versions that would cause configuration differences.

I have tried activating mod_heartmonitor and mod_heartbeat from my configuration file, but the notice still appeared.  I also tried activating mod_slotmem_plain with the same result.


-----

Dominic R. Jones, Ph.D.

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

             reply	other threads:[~2016-07-25 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 23:14 Dominic.R.Jones [this message]
2016-07-26 16:04 ` Achim Gratz
2016-07-26 19:18 Dominic.R.Jones
2016-08-04 23:43 Dominic.R.Jones

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=9820E0FA51BA9E488013F2BC442C0A6D63E816@006FCH1MPN2-072.006f.mgd2.msft.net \
    --to=dominic.r.jones@faa.gov \
    --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).