Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM as a Cloud SDK Dispatcher fails

Avatar

Level 2

My Dispatcher is failing with the error Function not implemented: AH00023: Couldn't create the proxy mutex 

 

Looking around, this may be something that can be fixed in the apache2.conf

Is this something I can edit?

 

Full trace below

 

dispatcher-sdk-2.0.81 % ./bin/docker_run.sh src host.docker.internal:4503 8080

values.csv not found in deployment folder: /Users/tim/aem-sdk/dispatcher/dispatcher-sdk-2.0.81/src - using files in 'conf.d' and 'conf.dispatcher.d' subfolders directly

processing configuration subfolder: conf.d

processing configuration subfolder: conf.dispatcher.d

Running script /docker_entrypoint.d/10-check-environment.sh

Running script /docker_entrypoint.d/15-check-pod-name.sh

Running script /docker_entrypoint.d/20-create-docroots.sh

Running script /docker_entrypoint.d/30-wait-for-backend.sh

Waiting until host.docker.internal is available

host.docker.internal resolves to 192.168.65.2

Running script /docker_entrypoint.d/40-generate-allowed-clients.sh

Running script /docker_entrypoint.d/50-check-expiration.sh

Running script /docker_entrypoint.d/60-check-loglevel.sh

Running script /docker_entrypoint.d/70-check-forwarded-host-secret.sh

Running script /docker_entrypoint.d/80-frontend-domain.sh

Starting httpd server

Tue Dec 28 22:26:28 UTC 2021 Monitoring reload trigger file existence at /etc/httpd/reload seconds started

Setting up watches.

Watches established.

[Tue Dec 28 22:26:28.711972 2021] [core:emerg] [pid 1:tid 274904324936] (38)Function not implemented: AH00023: Couldn't create the proxy mutex 

[Tue Dec 28 22:26:28.713744 2021] [proxy:crit] [pid 1:tid 274904324936] (38)Function not implemented: AH02478: failed to create proxy mutex

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@tgoodman_mediamonks wrote:

Thanks Jörg_Hoh ! 

 

Just confirming yes - it is the latest Dispatcher SDK - aem-sdk-dispatcher-tools-2.0.81-unix

I am having a problem with it on an M1 ARM Macbook Pro

I have also tried running it on an Intel Macbook Pro, and it works fine.


Ok, this shows that it's a platform issue... Hard to diagnose without having access to an M1-based machine 😞

 

Please raise a ticket with the support, this should be really handled with priority.

 

Have a good and healthy 2022!

View solution in original post

7 Replies

Avatar

Community Advisor

Looks like a bigger issue, raise it to clientcare@adobe.com

Avatar

Employee Advisor

Are you using the latest dispatcher SDK version? Are you activating a module which is supposed to use mod_proxy? 

(And yes, please reach out to customer care)

Avatar

Level 2

Thanks Jörg_Hoh ! 

 

Just confirming yes - it is the latest Dispatcher SDK - aem-sdk-dispatcher-tools-2.0.81-unix

I am having a problem with it on an M1 ARM Macbook Pro

I have also tried running it on an Intel Macbook Pro, and it works fine.

 

From this research online, it appears that this is a permissions issue.  I could change my http conf to change the mutex settings, which would get around the issue - Is it possible to set those flags in the conf.d settings for AEM as a Cloud?

https://ruungji.tistory.com/entry/Apache2-Function-not-implemented-AH00023

https://serverfault.com/questions/1014620/permission-denied-ah02478-failed-to-create-proxy-mutex

 

 

I also saw this post from someone with a similar setup, but it was an older version, I didn't have the same issue.

The Dispatcher gave a warning about the emulator before I added this to the dispatcher_run.sh environment variables

I also got the mutex error when I ran without this flag

 

 

--platform linux/amd64

 

 

Avatar

Correct answer by
Employee Advisor

@tgoodman_mediamonks wrote:

Thanks Jörg_Hoh ! 

 

Just confirming yes - it is the latest Dispatcher SDK - aem-sdk-dispatcher-tools-2.0.81-unix

I am having a problem with it on an M1 ARM Macbook Pro

I have also tried running it on an Intel Macbook Pro, and it works fine.


Ok, this shows that it's a platform issue... Hard to diagnose without having access to an M1-based machine 😞

 

Please raise a ticket with the support, this should be really handled with priority.

 

Have a good and healthy 2022!

Avatar

Level 2

Also - regarding your question regarding mod proxy  - No

 

This error occurs running either the default dispatcher src bundled with the SDK or the WKND dispatcher config.

Avatar

Level 1

@tgoodman_mediamonks were you able to resolve this issue? I'm facing it as well 😞