https://bz.apache.org/bugzilla/show_bug.cgi?id=66131
--- Comment #3 from Jérôme Billiras <[email protected]> --- With only `mod_heartmonitor` enabled `httpd -M` > Loaded Modules: > core_module (static) > so_module (static) > http_module (static) > watchdog_module (shared) > authz_core_module (shared) > heartmonitor_module (shared) > mpm_event_module (shared) > status_module (shared) > unixd_module (shared) > version_module (shared) I've got : `httpd -DFOREGROUND` > 2022-06-20 14:16:04.651920 heartmonitor:emerg - AH02284: failed to lookup > provider 'shm' for 'slotmem', maybe you need to load mod_slotmem_shm? > [Mon Jun 20 14:16:04.652112 2022] [:emerg] [pid 609:tid 140161243819328] > AH00020: Configuration Failed, exiting If a add directive `HeartbeatMaxServers 0` like it really was in <= 2.4.53 I've got : `httpd -DFOREGROUND` > AH00526: Syntax error on line 4 of /etc/httpd/mods-enabled/heartmonitor.load: > HeartbeatMaxServers: Should be bigger than 10 And obviously if I enable `mod_slotmem_shm` (and comment out `HeartbeatMaxServers 0`) I've got : `httpd -DFOREGROUND` > 2022-06-20 14:21:31.070000 mpm_event:notice - AH00489: Apache/2.4.54 (Unix) > configured -- resuming normal operations > 2022-06-20 14:21:31.070155 mpm_event:info - AH00490: Server built: Jun 20 > 2022 14:11:05 > 2022-06-20 14:21:31.070179 core:notice - AH00094: Command line: 'httpd -D > FOREGROUND' Indeed, it better to use shared memory instead of file based, and, if I have to use one I'll choose slotmem_shm. But I don't use either one, it's my automatic container builder that report me an error during config test. As things stand, it's impossible to use file based storage. So, either we apply this little patch which revert the possibility of using the file based storage, or we must completely wipe out the file based storage reference in module and doc. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
