Bug#750683: systemd: oneshot services get started more than once

[Michael Biebl]

Am 05.06.2014 18:42, schrieb Ed Swierk:
> Package: systemd
> Version: 208-1
> Severity: normal
> X-Debbugs-CC: pkg-systemd-maintainers at lists.alioth.debian.org
> 
> 
> Dear Maintainer,
> 
> During boot, certain services with Type=oneshot are started more than
> once. The set of affected services varies between boots, but almost
> always includes systemd-journal-flush.service and
> systemd-random-seed.service.

This is odd. I can't seem to reproduce this.
Can you find out what triggers the repeated start of those services?


> The services don't seem to mind--they return with status=0/SUCCESS.
> But occasionally a service gets started so many times that systemd
> itself marks it as failed (Result: start-limit) and prints a big red
> FAILED on the console.
> 
> I found that adding RemainAfterExit=yes to the service file prevents
> this from happening. But nothing in the systemd documentation (nor in
> the code, to the extent I understand it) indicates that this is
> necessary for oneshot services.

..

> The output of systemctl status and show are included below. I'd
> appreciate any suggestions on debugging this further.

I'd run with debugging enabled, i.e. use systemd.log_level=debug
This should give you a verbose log which you can query via journalctl -b.

See also http://freedesktop.org/wiki/Software/systemd/Debugging/


-- 
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: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140606/c8441643/attachment-0002.sig>