[systemd-bugs] [Bug 86415] New: systemd logs useless "mystery" warnings to the journal - log message fails to reference the source.

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86415

            Bug ID: 86415
           Summary: systemd logs useless "mystery" warnings to the journal
                    - log message fails to reference the source.
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: james at nurealm.net
        QA Contact: systemd-bugs at lists.freedesktop.org

Version: systemd 217-6 on Arch Linux

The new version 2.0.0 of cups has changed the unit file names from the form
"cups.service" to "org.cups.cupsd.service".  While the name change seems
gratuitous, there is still "something" which attempts to access the old unit
file names.  Upon reboot, with kernel loglevel=6, when cupsd starts, and
various other times, "journalctl -b" shows warnings like:

systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit
cups.socket failed to load: No such file or directory.
systemd[1]: Cannot add dependency job for unit cups.path, ignoring: Unit
cups.path failed to load: No such file or directory.
systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Invalid
argument
systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Invalid
argument
systemd[1]: Cannot add dependency job for unit cups.service, ignoring: Invalid
argument
systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit
cups.socket failed to load: No such file or directory.

The problem is this:  What program or configuration file caused the references
to "cups.socket", "cups.path", and "cups.service"?  The systemd journal does
not say, and there is no such reference in any unit file in /usr/lib/systemd/
or in /etc/systemd/.

In fact, the warning is practically useless, simply because it does not
disclose the source or cause of the warning.  Neither supernatural divination
nor grep has been effective in finding the source of these references thus far.

Unless these messages are meant to say that "systemd" is the source of the
explicit reference to "cups.socket"?  But there is no string "cups" in
"/usr/lib/systemd/systemd".

Please include the _source_ of systemd warnings in the systemd warning
messages.


Thanks
James

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141117/05c394c0/attachment.html>