[systemd-devel] Help with Systemd + Apache 2.4 - CentOS 7

Colin Guthrie gmane at colin.guthr.ie
Tue Nov 24 10:14:40 UTC 2020


Lucas Possamai wrote on 23/11/2020 21:57:
> I don't find any extra info in the Apache Logs. The attached error message
> is the only log I can see.

You will get more info by running e.g. systemctl status httpd.

As others have hinted at, if the systemd unit for httpd is using
Type=notify, you must make sure that the mod_systemd httpd module is
loaded and installed (it should be installed).

If this is the cause, you should see appropriate error messages in the
status output from above and the start command should take some time to
fail (usually a timeout of 1.5minutes or so.

On CentOS 7 this configuration is from
/etc/httpd/conf.modules.d/00-systemd.conf so perhaps double check you've
not disabled this configuration somehow with your setup?

Also, make sure that you've not manually started apache outside of
systemd. If it's running already (but not managed by systemd) systemd
will try and start it again, but won't be able to as the bound TCP ports
are already grabbed by the other instance.

Anyway, it'll take more info for someone to help you but it's very much
a configuration/usage issue rather than a fundamental systemd bug or
problem.

Good luck.

Col




More information about the systemd-devel mailing list