Bug#800087: systemd lists running daemons as failed after reboot

[Michael Biebl]

Control: tags -1 + moreinfo

Am 26.09.2015 um 18:08 schrieb James Bottomley:
> Package: systemd
> Version: 226-3
> Severity: normal
> 
> rebooting the current system often causes listed init system failures.
> in addition to failing to start spamd (listed under separate bug).
> Systemd thinks units have failed when, in fact, they're running.  The
> most common units for this are apache2 and mysql.
> 
> This is the state of a recent reboot, where apache2 is listed as failed
> 
> bedivere:~# systemctl --failed
>   UNIT            LOAD   ACTIVE SUB    DESCRIPTION
> ● apache2.service loaded failed failed LSB: Apache2 web server
> 
> LOAD   = Reflects whether the unit definition was properly loaded.
> ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
> SUB    = The low-level unit activation state, values depend on unit type.
> 
> 1 loaded units listed. Pass --all to see loaded but inactive units, too.
> To show all installed unit files use 'systemctl list-unit-files'.
> 
> Whereas ps shows it to be running

What's the output of
systemctl status apache2.service ?


-- 
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://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150930/35de0abd/attachment.sig>