<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - systemd logs useless "mystery" warnings to the journal - log message fails to reference the source." href="https://bugs.freedesktop.org/show_bug.cgi?id=86415#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - systemd logs useless "mystery" warnings to the journal - log message fails to reference the source." href="https://bugs.freedesktop.org/show_bug.cgi?id=86415">bug 86415</a> from <a class="email" href="mailto:james@nurealm.net" title="James <james@nurealm.net>"> James</a> <pre>Ok, I found the source of these, with a little help from someone having a better grasp of systemd. Silly me - I was looking for a reference from within the unit files, rather than a reference from the systemd/system/ directories. The messages are generated from left-over links in /etc/systemd/system/{multi-user.target.wants/cups.path, printer.target.wants/cups.service, sockets.target.wants/cups.socket} to non-existent unit files in /usr/lib/systemd/system/. So, is there some way, in this case, to have an explicit reference back to the broken link? Something like: From /etc/systemd/system/sockets.target.wants/cups.socket - Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. and From /etc/systemd/system/printer.target.wants/cups.service - Cannot add dependency job for unit cups.service, ignoring: Invalid argument Or - perhaps systemd could be a little smarter about not following broken links. The log message could then say something more direct, like: /etc/systemd/system/printer.target.wants/cups.service: No such file or directory.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>