[systemd-bugs] [Bug 75680] New: systemd-notify notifications often lost

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 75680
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: systemd-notify notifications often lost
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: jan.steffens at gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I have a shell script service here using systemd-notify for readiness and
watchdog, with NotifyAccess=all. In the journal I often see messages like
"systemd[1]: Cannot find unit for notify message of PID 9834", with subsequent
watchdog timeouts by my service.

Is systemd trying to find out the unit of the notification sender, but the
sender (a forked systemd-notify) has already terminated?

Sometimes it even happens when the service is started, so the READY message is
lost.

I think this currently makes systemd-notify useless.

systemd 210

-- 
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/20140302/5fd77ca1/attachment.html>