Red Hat Bugzilla – Bug 982376
systemd-notify doesn't work, since it lives too short
Last modified: 2016-01-25 16:25:43 EST
+++ This bug was initially created as a clone of Bug #820448 +++
Using a test systemd service unit with
and using a test script that contains
the notify is sometimes successfull and sometimes it fails with the following message in /var/log/messages
May 10 00:37:31 laptop systemd: Cannot find unit for notify message of PID 3495.
when the command is successfull
> sudo systemctl start test1.service
returns almost immediately, when it fails it times out after 90 seconds
below are the files I am using along package versions
$ rpm -qa | grep -i -e systemd
$ cat /lib/systemd/system/test1.service
$ cat /tmp/testservice
--- Additional comment from Michal Schmidt on 2012-05-10 04:36:44 EDT ---
(In reply to comment #0)
> May 10 00:37:31 laptop systemd: Cannot find unit for notify message of PID
systemd-notify sends a message to $NOTIFY_SOCKET and then exits.
When systemd receives the notification, the systemd-notify process may have already exited and been reaped by bash.
Ideally the cgroups membership information would be delivered with the message over the socket.
* An auxiliary meta data message for AF_UNIX called SCM_CGROUPS (or something like that), i.e. a way to attach sender cgroup membership to messages sent via AF_UNIX. This is useful in case services such as syslog shall be shared among various containers (or service cgroups), and the syslog implementation needs to be able to distinguish the sending cgroup in order to separate the logs on disk. Of course stm SCM_CREDENTIALS can be used to look up the PID of the sender followed by a check in /proc/$PID/cgroup, but that is necessarily racy, and actually a very real race in real life.
As an alternative fix, the notification could be made synchronous.
--- Additional comment from Alan Pevec on 2012-06-27 13:41:54 EDT ---
(In reply to comment #1)
> systemd-notify sends a message to $NOTIFY_SOCKET and then exits.
> When systemd receives the notification, the systemd-notify process may have
> already exited and been reaped by bash.
So, as a work-around, daemon process itself should send READY=1 to $NOTIFY_SOCKET
instead of forking "systemd-notify" command.
We need this for openstack daemons, here's _untested_ code in Python
(after sd_notify implementation in sd-daemon.c):
s = socket.socket(socket.AF_UNIX, socket.SOCK_DGRAM)
e = os.getenv('NOTIFY_SOCKET')
--- Additional comment from Alan Pevec on 2012-09-18 10:43:15 EDT ---
Script in comment 2 doesn't work with systemd-188-3.fc18 where NOTIFY_SOCKET is abstract namespace socket:
It needs special handling if notification socket starts with @: convert to bytes and replace '@' with 0.
--- Additional comment from Alan Pevec on 2012-09-18 18:36:01 EDT ---
Patch for example script in comment 2:
e = os.getenv('NOTIFY_SOCKET')
+ # abstract namespace socket
+ e = '\0%s' % e[1:]
--- Additional comment from Fedora End Of Life on 2013-04-03 13:44:40 EDT ---
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
The original bug has been fixed a long time ago.
This still does not work from systemd point of view.