[systemd-devel] problem apache2 service

Lennart Poettering lennart at poettering.net
Thu Jan 12 09:09:53 UTC 2017


On Thu, 12.01.17 09:12, Nico - Clicom snc - www.clicom.it (nico at clicom.it) wrote:

> I have this error on my nas:
> -- Unit apache2-safe.service has begun starting up.
> Jan 12 08:55:47 ReadyNESSY systemd[5020]: apache2-safe.service: Failed at
> step EXEC spawning /usr/sbin/apache2: No such file or directory
> -- Subject: Process /usr/sbin/apache2 could not be executed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- The process /usr/sbin/apache2 could not be executed and failed.
> 
> /usr/sbin/apache2 is a link:
> 
> root at ReadyNESSY:~# ls -l /usr/sbin/apache2
> lrwxrwxrwx 1 root root 33 Sep 23 20:53 /usr/sbin/apache2 ->
> ../lib/apache2/mpm-worker/apache2

The help text you saw is a bit misleading. While systemd generates the
error, it doesn't cause it. Most likely your /usr/sbin/apache2 binary
cannot be started because itself or its dynamic loader or so is
missing. Consider invoking the binary from the shell, and see if that
works.

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list