Dispatcher: Apache unable to start. | Community
Skip to main content
ronnyfm
ronnyfm
Level 4
May 31, 2018
Solved

Dispatcher: Apache unable to start.

  • May 31, 2018
  • 7 replies
  • 7804 views

Hello, I am facing a weird issue installing a dispatcher for an author instance.

The configuration for the author is based in a previous installation that I know it works fine.

Now back to this project, the dispatchers for the publish instances are working fine. They do have the same httpd version, same RHEL version, same dispatcher module (I even copied the same .so from the working dispatchers).

But Apache is unable to start and I do not have many useful info, since Apache doesn't write to the error_log, also dispatcher.log is not even created. 

apachectl configtest

output says the syntax is OK.

In fact, if I remove all the dispatcher configuration, and only try to load the module, Apache fails. So, I suspect is something with the .so itself, but as I said, it is the same exact file in the working dispatchers.

Any hints or actions in order to get a more verbose output? Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ronnyfm

Thanks. I was able to solve it running the following command:

sudo chcon -t httpd_sys_script_exec_t /etc/httpd/modules/mod_dispatcher.so

7 replies

pgleghorn
pgleghorn
Level 2
May 31, 2018

If you aren't getting any logging at all to error_log, then it seems likely that apache httpd is writing all it's messages somewhere else. Do you get any messages in error_log when you remove the dispatcher .so from httpd configuration and startup apache successfully? If not, then check the ServerRoot, ErrorLog and LogLevel directives to be sure where to look for the log. if you find where httpd is writing the error log then try setting "LogLevel debug" and restart - that should make the dispatcher module announce itself in the error log at startup.

Phil

ronnyfm
ronnyfmAuthorAccepted solution
Level 4
May 31, 2018

Thanks. I was able to solve it running the following command:

sudo chcon -t httpd_sys_script_exec_t /etc/httpd/modules/mod_dispatcher.so
joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 3, 2018

Hi,

just to make sure: Is this a documented setting you just forgot to apply? Or is this something you had to apply on top of all the steps documented to run dispatcher with selinux?

Jörg

pgleghorn
pgleghorn
Level 2
June 3, 2018

Interestingly some steps for dispatcher with selinux are documented here Installing Dispatcher , but it doesn't mention the httpd_sys_script_exec_t context.

Phil

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 3, 2018

That's interesting, because the documented way worked well with RHEL and Apache 2.2. And according to SELinux/apache - Fedora Project Wiki this context applies to CGI scripts (or other executables).

What version of Apache httpd and which Redhat version are you using?

Jörg

ronnyfm
ronnyfmAuthor
Level 4
June 4, 2018

Yeah, I sometimes forget to document all differences when selinux appears to be an issue, but I was with the latest dispatcher version, latest Apache 2.4.6 and latest RHEL. After solving this issue, I also had to fix permissions for the docroot, though I applied the commands found in the Installation guide. I solved by following the solution found here: centos7 - CentOs 7 & SELInux: User cant write in the Webroot of Apache - Server Fault

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 4, 2018

Hi,

would you be so kind and raise a Daycare ticket, describe your setup and the additional steps you had to make to get your system up and running? Based on that Adobe Support should be able to validate the documentatino and update it accordingly.

Thanks for your help,

Jörg

Terms & ConditionsAccessibility statement

Loading footer...