Am 12.01.2017 um 09:12 schrieb Nico - Clicom snc - www.clicom.it:
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
this is *not* a systemd problem and that support hint *really* should
have been removed long ago by the systemd-developers because it will
always appear for functional analphabets that systemd is the cause and
not the messenger of teh problem
that is a pretty clear message
/usr/sbin/apache2: No such file or directory
lrwxrwxrwx 1 root root 33 Sep 23 20:53 /usr/sbin/apache2 ->
../lib/apache2/mpm-worker/apache2
so /usr/lib/apache2/mpm-worker/apache2 don't exist, either fix ExecStart
in the systemd-unit or just look why your setup is mising files
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
