Bug#768168: watchdog does not start at boot

Michael Biebl biebl at debian.org
Wed Nov 12 14:17:22 GMT 2014


Am 12.11.2014 um 14:44 schrieb Michael Biebl:
> Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
>> On Nov 11, Michael Biebl wrote:
>>> Please boot with systemd.log_level=debug on the kernel command line, the
>>> attach the output of "journalctl -alb"
>>
>> I guess these are the relevant lines:
>>
>>   Found ordering cycle on graphical.target/start
>>   Found dependency on multi-user.target/start
>>   Found dependency on watchdog.service/start
>>   Found dependency on graphical.target/start
>>   Breaking ordering cycle by deleting job watchdog.service/start
>>
> 
>> [Unit]
>> After=runlevel1.target runlevel2.target runlevel3.target runlevel4.target runlevel5.target

[..]

>> [Install]
>> WantedBy=multi-user.target


That's the part that causes the dep cycle afaics.

By being hooked into multi-user.target, watchdog.service will have an
explicit
Before=multi-user.target
dependency.

multi-user.target on the other hand is an alias of runlevel2.target,
runlevel3.target and runlevel4.target and you explicitly requested
After=runlevel1.target runlevel2.target runlevel3.target
runlevel4.target runlevel5.target

Those are conflicting requirements, so systemd will drop the unit.


-- 
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/20141112/85d49945/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list