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

[Michael Biebl]

Am 05.10.2015 um 01:48 schrieb 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.

You might need to have give apache more time to start up. Maybe 20 secs
is not enough since during boot there is a lot of other I/O going on and
the apache control process kills itself prematurely:


> Oct 03 10:45:06 bedivere apache2[693]: Starting web server: apache2AH00180: WARNING: MaxRequestWorkers of 20 exceeds ServerLimit value of
> Oct 03 10:45:06 bedivere apache2[693]: 5 servers, decreasing MaxRequestWorkers to 5.
> Oct 03 10:45:06 bedivere apache2[693]: To increase, please see the ServerLimit directive.
> Oct 03 10:45:42 bedivere apache2[693]: failed!
> Oct 03 10:45:42 bedivere apache2[693]: The apache2 instance did not start within 20 seconds. Please read the log files to discover problems ... (warning).
> Oct 03 10:45:42 bedivere systemd[1]: apache2.service: Control process exited, code=exited status=1




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151005/fc99104f/attachment-0002.sig>