How to get rid of managed rewrite maps error messages in dispatcher log | Community
Skip to main content
MeasurableBusinessResults
MeasurableBusinessResults
Level 3
October 13, 2025
Question

How to get rid of managed rewrite maps error messages in dispatcher log

  • October 13, 2025
  • 2 replies
  • 430 views

In my dispatcher_httpderror log, I keep getting the following messages.

 

Fri Oct 10 23:59:24.646793 2025 [managed_rewrite_maps:debug] [pid 123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check in progress
Fri Oct 10 23:59:24.650947 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] No managed rewrite maps configured
Fri Oct 10 23:59:24.655150 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check DONE
Fri Oct 10 23:59:24.659466 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] Waiting for 30 seconds for next managed rewrite maps check

 

I am not using any Apache RewriteMap directive on my setup.
These errors pollute my log and have no value, how can I get rid of them?
And I want to keep the debug level, so that I can see the REAL errors 

2 replies

Karishma_begumSh
Karishma_begumSh
Level 4
October 13, 2025

Hi @measurablebusinessresults 

These repeated managed_rewrite_maps:debug messages from mod_rewrite’s managed rewrite map feature that was introduced in Apache 2.4.54+. Even if you don’t use any RewriteMap directives, Apache still runs an internal periodic check for "managed maps," which produces these noisy debug log entries.

Override the log level per module
Disable debug logs from the managed_rewrite_maps module while keeping debug elsewhere.
In your Apache configuration (httpd.conf or equivalent, e.g. /etc/httpd/conf/httpd.conf or /etc/apache2/apache2.conf), add below

apache

RewriteOptions DisableManagedMaps LogLevel debug LogLevel managed_rewrite_maps:error

then reload apache

sudo systemctl reload httpd

 

Try using above,hope this helpful 🙂

 

Regards,

Karishma.

    MeasurableBusinessResults
    MeasurableBusinessResultsAuthor
    Level 3
    October 14, 2025

    Thanks, sounds reasonable.

    I tried to apply this.

    There is a default LogLevel directive in dispatcher_vhost.conf but that is an immutable file.
    Multiple LogLevel directives are fine for Apache, so I added it in one of the custom vhost configs

    Now the 

    managed_rewrite_maps:debug

    errors are gone from dispatcher_httpderror_*
    But there is nothing else, the log file is essentially empty

    My effective LogLevel settings are:

    # dispatcher_vhost.conf (immutable) LogLevel dispatcher_module:Warn rewrite_module:Warn # custom.vars LogLevel managed_rewrite_maps:error # in rewrite rules for one vhost only LogLevel rewrite:trace5



    Side note:
    I also wonder why Adobe would make such a noisy log the default for cloud instances, especially when it serves no purpose as sites do not use managed maps by default.

    MeasurableBusinessResults
    MeasurableBusinessResultsAuthor
    Level 3
    October 14, 2025

    Actually this does not work, the Adobe cloud pipeline fails

    2025/10/14 12:11:35 Apache configuration uses non-allowlisted directives: conf.d/variables/custom.vars:43: LogLevel conf.d/variables/custom.vars:43: LogLevel conf.d/rewrites/lfg_rewrite.rules:26: LogLevel
    MeasurableBusinessResults
    MeasurableBusinessResultsAuthor
    Level 3
    November 3, 2025

    The solution is to just set the global LogLevel to warn in the custom vars, since debugging with a more detailed log level is not possible anyway in the cloud.

    Terms & ConditionsAccessibility statement

    Loading footer...