Expand my Community achievements bar.

SOLVED

Dispatcher for Mac OS 10.14 Mojave

Avatar

Community Advisor

I recently received an upgraded Mac laptop with Mac OS 10.14 Mojave. While setting up Dispatcher in my mac laptop I faced numerous issues and finally ended up with not setting up any.

Here are my research and analysis. I hope it will be helpful for others.

1) Mac OS 10.14 Mojave doesn't allow to copy dipatcher_module.so file into /usr/libexe/apache2 folder even as the root user. In case, if you still want to copy it, disabling SIP at OS booting by going into Debug mode is the only option(Found this on Google search, didn't try it though).

2) As I couldn't copy the dispatcher_module.so file into /usr/libexe/apache2 folder, I tried to load it from another location like /usr/local/etc/apache2/, below is the error message I received.

httpd: Syntax error on line xxx of /private/etc/apache2/httpd.conf: Cannot load /usr/local/etc/apache2/mod_dispatcher.so into server: dlopen(/usr/local/etc/apache2/mod_dispatcher.so, 10): no suitable image found.  Did find:\n\t/usr/local/etc/apache2/mod_dispatcher.so: code signature in (/usr/local/etc/apache2/mod_dispatcher.so) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.\n\t/usr/local/etc/apache2/mod_dispatcher.so: stat() failed with errno=22

3) After doing some research around the above error message, I found that starting Mac OS 10.14 Mojave, OOTB Apache2 doesn't load unsigned apache modules anymore and thApachehe module I downloaded from https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher.html for Mac OS has not been signed.

4) As above route didn't fetch me any results, I tried to setup dispatcher using Homebrew Apache and later realized that Adobe Dispatcher module for Mac OS is not compatible with Homebrew apache version.

5) Currently, I have installed VirtualBox on my Mac and installed Ubuntu OS to setup dispatcher.

My currently local setup looks like below.

1) Author on port 4502 on Mac OS

2) Publish on port 4503 on Mac OS

3) Dispatcher on Ubuntu OS installed on VirtualBox on Mac OS. We need to setup "host-only adapter" on network setting in VirtualBox.

4) In dispatcher.any file, use "10.0.2.2" with port "4503" om renders to connect to publish instance from VirtualBox Ubuntu OS.

I feel that Engineering team at Adobe should plan about releasing new signed Dispatcher module for Mac OS.

1 Accepted Solution

Avatar

Correct answer by
Level 1

This has been fixed, please use step 1 for Mojave. It's working for me.

Adobe Experience Manager Help | Set up AEM Dispatcher on macOS

View solution in original post

4 Replies

Avatar

Administrator

Joerg Hoh ​ Request you help here.



Kautuk Sahni

Avatar

Employee Advisor

The problem is that the dispatcher binary is not signed, which is required by OSX 10.14 (Mojave).

At the moment I only know this workaround; it basically creates a new httpd instance you need to manage on your own. But it's only a workaround, so please raise a Daycare ticket to request a signed binary.

$ mkdir -p ~/Applications/apache2/bin

$ cp /usr/sbin/httpd ~/Applications/apache2/bin

$ codesign --remove-signature ~/Applications/apache2/bin/httpd

$ cp /etc/apache2/http.conf ~/Applications/apache2

$ cd ~/Applications/apache2

$ sudo bin/httpd -k start -d . -f httpd.conf

I would not recommend to run this on any other setup as your own local development machine.

Avatar

Correct answer by
Level 1

This has been fixed, please use step 1 for Mojave. It's working for me.

Adobe Experience Manager Help | Set up AEM Dispatcher on macOS

Avatar

Level 5

I see this has been resolved but adding my comments if that helps any future visitors

 

First of all, when you say in step 1, "doesn't allow to copy dipatcher_module.so file into /usr/libexe/apache2", I think dispatcher module should not be added in Apache module because if there is an update in Apache application you might loose your module. Better to add it under "/private/libexec/apache2/mod_dispatcher.so" or somewhere else.

 

And for the authority issue, I had the similar issue and I posted my detailed answer on other thread

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dispatcher-so-file-not-loa...