Summary: | =www-servers/apache-2.4.18 - apache2 has detected an error in your setup: AH00526: Syntax error on line 110 of /etc/apache2/modules.d/00_default_settings.conf: Invalid command 'Require', perhaps misspelled or defined by a module not included in the server | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | arthur |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 468302 |
Description
Jeroen Roovers (RETIRED)
2016-02-25 05:26:55 UTC
Hello! I don't know if this bug is up to date. Because today emerge disgorges a warning when i emerge apache without some Modules or useflags. Like... =============================== * Module 'authz_core' is required in the default apache configuration. * Module 'socache_shmcb' is required in the default apache configuration. * * You have disabled one or more required modules * for the default apache configuration. * Although this is not an error, please be * aware that this setup is UNSUPPORTED. =============================== * Warning: Critical module not installed! * Modules 'authn_core', 'authz_core' and 'unixd' * are highly recomended but might not be in the base profile yet. * Default config for ssl needs module 'socache_shmcb'. * Enabling the following flags is highly recommended: * + apache2_modules_authn_core ============================== The solution was, as suggested to set the Useflag "apache2_modules_authn_core apache2_modules_unixd" and add the missing modules to the make.conf. @jer: You need the authz_core module. Our default configuration (and basically every real configuration) requires it. # critical modules for the default config MODULE_CRITICAL=" authn_core authz_core authz_host dir mime unixd " The warning comes in pkg_postinst() which isn't ideal if you've accidentally broken your Apache. On the other hand, some of those are more critical than others, and if you mess with the default config a bit you can easily get away without e.g. authz_host. So it would be overkill to have the user set something like I_KNOW_WHAT_I_AM_DOING. (In reply to Michael Orlitzky from comment #2) > @jer: You need the authz_core module. Our default configuration (and > basically every real configuration) requires it. But these are simply USE flags so you could very well set REQUIRED_USE to define (and fail on bad) flags being set. And pkg_postinst() would be too late whereas REQUIRED_USE would bail out before the build. How could REQUIRED_USE replace the current warnings? Also, I don't think this should block all the stabilization (well, the warning is really clear about what people can expect when disabling the USE) |