FS#37012 - [systemd] new weird messages on boot

Attached to Project: Arch Linux
Opened by Lorenzo Porta (Vindex17) - Saturday, 21 September 2013, 16:05 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 25 September 2013, 16:34 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

set 21 17:58:10 localhost systemd[1]: Cannot add dependency job for unit local-fs.target, ignoring: Unit local-fs.target failed to load: No such file or directory. See system logs and 'systemctl status local-fs.target' for details.
set 21 17:58:10 localhost systemd[1]: Cannot add dependency job for unit swap.target, ignoring: Unit swap.target failed to load: No such file or directory. See system logs and 'systemctl status swap.target' for details.
set 21 17:58:10 localhost systemd[1]: Cannot add dependency job for unit timers.target, ignoring: Unit timers.target failed to load: No such file or directory. See system logs and 'systemctl status timers.target' for details.
set 21 17:58:10 localhost systemd[1]: Cannot add dependency job for unit paths.target, ignoring: Unit paths.target failed to load: No such file or directory. See system logs and 'systemctl status paths.target' for details.
set 21 17:58:10 localhost systemd[1]: Cannot add dependency job for unit slices.target, ignoring: Unit slices.target failed to load: No such file or directory. See system logs and 'systemctl status slices.target' for details.

But systemctl reports all of them active and static...

Additional info:
* package version: 207-5
I had none of these messages with systemd 204

Steps to reproduce:
every boot/reboot
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 25 September 2013, 16:34 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Harmless "errors". Consider the systemd hook to still be a WIP.
Comment by Tom Gundersen (tomegun) - Saturday, 21 September 2013, 22:50 GMT
I assume these are from the systemd initrd hook? If so, it is nothing to worry about, but we should at some point avoid the warnings by either including the unit files in the initrd or making sure that no other units in the initrd Wants them.
Comment by Dave Reisner (falconindy) - Saturday, 21 September 2013, 23:00 GMT
Yeah, they're from the initramfs. Nothing to do here...

Loading...