Répondu

Pipeline-free URL Redirects is not working in AEM Cloud Dispatcher

Forum|Forum|1 year ago
November 6, 2024
3 commentaire
2569 vue

Hi All, I am trying to implement the Redirect Map Manager in AEM Cloud as per the below documentation
https://adobe-consulting-services.github.io/acs-aem-commons/features/redirect-map-manager/index.html

Redirect map manager is working in AEM Cloud latest i created the entries then i followed the below documentation for configuring the dispatcher for rewrites
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/pipeline-free-url-redirects

I have created the managed-rewrite-maps.yaml file and added the below code
maps:
- name: my.map
path: /content/dam/redirectmaps/mysite-redirectmap.txt

i have the redirectmap file in the mentioned location and added this in rewrite.rules
# RewriteMap from managed rewrite maps
RewriteMap map.foo dbm=sdbm:/tmp/rewrites/my.map
RewriteCond ${map.foo:$1} !=""
RewriteRule ^(.*)$ ${map.foo:$1|/} [L,R=301]

I am getting the error as below
AH00526: Syntax error on line 11 of /etc/httpd/conf.d/rewrites/rewrite.rules:
RewriteMap: file for map map.foo not found:/tmp/rewrites/my.map.dir

tried to use different paths in rewrite.rules
RewriteMap map.foo txt:/content/dam/redirectmaps/mysite-redirectmap.txt

but it dint worked any help on how to get or reference the redirectmap file in aem cloud dispatcher.

Meilleure réponse par daniel-strmecki

Hi @saujanyagu,

your Dispatcher config looks ok, I suggest you check the following things:

As this feature has just been released, ensure that you are testing on the up-to-date instance of AEMaaCS
Ensure that your AEM Publisher is returning a valid map on the configured path
Check the Dispatcher logs, they contain detailed info on fetching and storing rewrite maps

[Mon Sep 23 11:01:23.374668 2024] [managed_rewrite_maps:debug] [pid 303] Starting monitoring of managed rewrite maps changes
[Mon Sep 23 11:01:23.381890 2024] [managed_rewrite_maps:debug] [pid 303] Waiting for 300 seconds for next managed rewrite maps check
[Mon Sep 23 11:01:54.604026 2024] [managed_rewrite_maps:debug] [pid 513] Managed rewrite maps configured in '/etc/httpd/opt-in/managed-rewrite-maps.yaml'
[Mon Sep 23 11:01:54.629172 2024] [managed_rewrite_maps:debug] [pid 513] mapping 'pilot.map' from path '/content/historical-locks/com-pilot.pilot-map.txt' with params wait = 'false' and ttl = '3600'
[Mon Sep 23 11:01:54.639099 2024] [managed_rewrite_maps:debug] [pid 513] checking time since last modification of '/tmp/rewrites/pilot.map.pag' > ttl '3600' seconds

Good luck,

Daniel

daniel-strmecki

Réponse

Community Advisor and Adobe Champion

Hi @saujanyagu,

your Dispatcher config looks ok, I suggest you check the following things:

As this feature has just been released, ensure that you are testing on the up-to-date instance of AEMaaCS
Ensure that your AEM Publisher is returning a valid map on the configured path
Check the Dispatcher logs, they contain detailed info on fetching and storing rewrite maps

[Mon Sep 23 11:01:23.374668 2024] [managed_rewrite_maps:debug] [pid 303] Starting monitoring of managed rewrite maps changes
[Mon Sep 23 11:01:23.381890 2024] [managed_rewrite_maps:debug] [pid 303] Waiting for 300 seconds for next managed rewrite maps check
[Mon Sep 23 11:01:54.604026 2024] [managed_rewrite_maps:debug] [pid 513] Managed rewrite maps configured in '/etc/httpd/opt-in/managed-rewrite-maps.yaml'
[Mon Sep 23 11:01:54.629172 2024] [managed_rewrite_maps:debug] [pid 513] mapping 'pilot.map' from path '/content/historical-locks/com-pilot.pilot-map.txt' with params wait = 'false' and ttl = '3600'
[Mon Sep 23 11:01:54.639099 2024] [managed_rewrite_maps:debug] [pid 513] checking time since last modification of '/tmp/rewrites/pilot.map.pag' > ttl '3600' seconds

Good luck,

Daniel

S

SaujanyaGuAuteur

Hi @daniel-strmecki ,

Thanks for the response.

I'm using the latest AEMaaCS version (Adobe Experience Manager 2024.10.18311.20241017T104455Z-241000).

The redirect map file only contains the following:

/test /content/test-project/us/en/qa/test.html

However, I’m unable to locate the logs you mentioned. Could you please guide me on how to access them?

Also, I created the managed-rewrite-maps.yaml file at this path:

C:\AEM\test-project\dispatcher\src\opt-in\managed-rewrite-maps.yaml

Is this the correct location?

Thanks for your help!

daniel-strmecki

Community Advisor and Adobe Champion

Hi @saujanyagu,

yes, that is the correct location. Make sure you have Dispatcher flexible mode enabled - USE_SOURCES_DIRECTLY, as this is a prerequisite.

The log entries I shared should be in the aemdispatcher log file. In case you don't see Dispatcher pulling the redirect maps successfully on regular internals it will not work. I suggest that you first test on the local SDK with a local Dispatcher so you can set the DEBUG log level.

Here is my example that is working fine:

Good luck,

Daniel

arunpatidar

Community Advisor

Hi @saujanyagu

Requires AEM CS release version 18311 or higher

Please check

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/pipeline-free-url-redirects

Past Cloud Service Releases

https://experienceleague.adobe.com/en/docs/experience-manager-release-information/aem-release-updates/update-releases-roadmap#past

Arun Patidar

V

vitali_breida

Hello

I have the same issue.

I have AEM SDK 18598 ( 2024.11.18598.20241113T125352Z) and ACS Commons 6.10, my local dispatcher (for AEMaaCS_ works correctly (validation , docker_run_hot_reload until I configure Rewrite Map according to the https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/pipeline-free-url-redirects

I see in the dispatcher logs:

Removing empty managed rewrite maps files for testing purposes
[Sun Feb 02 15:07:25.738469 2025] [managed_rewrite_maps:debug] [pid 1] Managed rewrite maps check in progress
[Sun Feb 02 15:07:25.741145 2025] [managed_rewrite_maps:debug] [pid 1] Managed rewrite maps configured in '/etc/httpd/opt-in/managed-rewrite-maps.yaml'
[Sun Feb 02 15:07:25.746821 2025] [managed_rewrite_maps:debug] [pid 1] map count = 1
[Sun Feb 02 15:07:25.755857 2025] [managed_rewrite_maps:debug] [pid 1] mapping 'my.map' from path '/etc/acs-commons/redirect-maps/my-redirect-map/_jcr_content.redirectmap.txt' with params wait = 'false' and ttl = '300' and probePath = '/system/probes/health'
[Sun Feb 02 15:07:25.758454 2025] [managed_rewrite_maps:debug] [pid 1] no map file '/tmp/rewrites/my.map.pag' exists yet - will generate for the first time
[Sun Feb 02 15:07:25.761062 2025] [managed_rewrite_maps:debug] [pid 1] checking if probe '/system/probes/health' is 200 OK
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
[Sun Feb 02 15:09:32.967829 2025] [managed_rewrite_maps:debug] [pid 1] probe '/system/probes/health' for map 'my.map' is NOT OK !!! - resp status code = '404'
[Sun Feb 02 15:09:32.969943 2025] [managed_rewrite_maps:debug] [pid 1] configured probe '/system/probes/health' for map my.map is NOT OK - won't proceed to fetch map data from unreliable source !!!
[Sun Feb 02 15:09:32.973632 2025] [managed_rewrite_maps:debug] [pid 1] No httpd PID file found at /run/apache2/httpd.pid for map data readiness signalling
[Sun Feb 02 15:09:32.975798 2025] [managed_rewrite_maps:debug] [pid 1] Managed rewrite maps check DONE
Running script /docker_entrypoint.d/zzz-overwrite_gitinit_metadata.sh
Starting httpd server
[Sun Feb 02 15:09:32.988028 2025] [managed_rewrite_maps:debug] [pid 721] Managed rewrite maps check in progress
Sun Feb 2 15:09:32 UTC 2025 Monitoring file changes on mount source at /mnt/dev/src started
Setting up watches. Beware: since -r was given, this may take a while!
[Sun Feb 02 15:09:32.993037 2025] [managed_rewrite_maps:debug] [pid 721] Managed rewrite maps configured in '/etc/httpd/opt-in/managed-rewrite-maps.yaml'
[Sun Feb 02 15:09:33.008392 2025] [managed_rewrite_maps:debug] [pid 721] map count = 1
[Sun Feb 02 15:09:33.016034 2025] [managed_rewrite_maps:debug] [pid 721] mapping 'my.map' from path '/etc/acs-commons/redirect-maps/my-redirect-map/_jcr_content.redirectmap.txt' with params wait = 'false' and ttl = '300' and probePath = '/system/probes/health'
[Sun Feb 02 15:09:33.018145 2025] [managed_rewrite_maps:debug] [pid 721] no map file '/tmp/rewrites/my.map.pag' exists yet - will generate for the first time
[Sun Feb 02 15:09:33.020751 2025] [managed_rewrite_maps:debug] [pid 721] checking if probe '/system/probes/health' is 200 OK
curl: (22) The requested URL returned error: 404
Watches established.
AH00526: Syntax error on line 133 of /etc/httpd/conf.d/rewrites/rewrite.rules:
RewriteMap: file for map my.map not found:/tmp/rewrites/my.map.dir

Could you please suggest what is wrong?

Best regards,

Vitali

W

wost

New Member

Hi @vitali_breida
I have exactly the same problem. But with SDK AEM SDK v2025.1.19352.20250131T194709Z-250100 (Dispatcher Tools 2.0.235 for Unix) and AEM commons Version: 6.9.6
I am curious, have you perhaps already found a solution?

Best regards
WitoldO

D

draganczukp

Me and my team spent a couple hours trying to debug this issue today. We came to the conclusion that the dispatcher distributed with the SDK is broken. More specifically, the script that handles the redirect map files (`/docker_run.d/35-update-managed-rewrite-maps.sh` in the container) doesn't set up file permissions properly when creating temporary files.

First, the `curl` call on line 104 fails when it tries to write to the temporary file. Changing the command from just `curl` to `as_apache curl` fixes this problem, revealing the permissions as the cause.

Then, the `cat` on line 82 (and the subsequent piped `awk`) has it's output redirected to another temporary file. This redirect also fails due to file permissions. Both of those issues could be fixed easily by running `chmod 666` on the temporary files, or perhaps not running them with `as_apache`.

Additionally, the whole script will run into 404 loop with no clear reason when running locally, as `/system/probes/health` returns with a 404 on the local SDK. Setting `MANAGED_REWRITE_MAPS_PROBE_CHECK_SKIP=true` when launching bypasses this issue, but it would be nice to see any mention of it in the logs, or somewhere in the documentation about the redirect maps.