You are not logged in.
Hey guys,
When running transmission as a systemd --user service and seeding some torrent I'm getting messages in the kernel ring buffer that look like this:
systemd[1]: Cannot find unit for notify message of PID 535where PID 535 is the transmission daemon.
Here's my systemd --user service file for transmission-daemon
[Unit]
Description=Transmission Bit Torrent Daemon
Documentation=man:transmission-daemon(1)
[Service]
ExecStart=/usr/bin/transmission-daemon --foreground
[Install]
WantedBy=console.targetI'm not really sure what this message means. Any insight is appreciated!
Last edited by EvanPurkhiser (2013-10-23 18:04:15)
Offline
I appear to have fixed this by changing my systemd/user/transmission.service to Type=notify.
Presumably the notification was bubbling up to the systemd[1] process and couldn't be handled there. I'm not entirely sure why transmission is sending out so many notifications (perhaps notifications for torrent status?)
Offline
A notification send via sd_notify is supposed to reach systemd; see the description of Type=notify in the systemd.service man page. The service file that comes with transmission does contain this type specification, so your copy was incomplete/outdated.
Offline
You're right. The problem was that I was running transmission as a systemd --user service without Type=notify, so the notification wasn't being handled by my systemd --user instance, and was being caught by the systemd --system instance, which doesn't know about the systemd --user transmission.service. So that's what the warning was from. (At least I think that's why!)
The reason mine didn't have the Type=notify was because I hadn't looked at the /systemd/system/transmission.service before writing mine =P
Last edited by EvanPurkhiser (2013-08-18 08:42:44)
Offline
Right, I didn't pay enough attention to the '[1]' part. Now the 'bubbling up' makes more sense ![]()
Offline