Bug#800087: closed by Michael Biebl <biebl at debian.org> (Re: Bug#800087: systemd lists running daemons as failed after reboot)

[James Bottomley]

On Sun, 2015-10-04 at 23:06 +0000, Debian Bug Tracking System wrote:
> Well, this is apparently an apache configuration problem, causing the
> service to return a non-zero exit code.
> 
> Once you fix that, the service should not be marked as failed.

That's pretty obviously an incorrect deduction, isn't it?  If it were a
config file problem leading to the control process erroring out then the
manual systemctl start apache would also fail; but, as you can see from
the description in the original report, it doesn't.

The logs have this in them:

[ 2015-10-03 10:41:55.6129 1309/b5cfeb40 age/Hel/Main.cpp:455 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)
[ 2015-10-03 10:41:55.6160 1319/b6960b40 age/Log/Main.cpp:349 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)
[ 2015-10-03 10:45:21.1489 1353/b5dfeb40 age/Hel/Main.cpp:455 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)
[ 2015-10-03 10:45:21.1521 1374/b68fab40 age/Log/Main.cpp:349 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown)

So apache dies because something external kills it during boot up.  Hm,
I wonder what that could be ...

James