Bug 403443 – net-p2p/transmission-2.42-r1 - /etc/init.d/transmission-daemon: start-stop-daemon: did not create a valid pid in `/var/run/transmission/transmission.pid'

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Sławomir Nizio 2012-02-13 18:30:42 UTC]

# /etc/init.d/transmission-daemon start
 * Starting transmission daemon ...
 * start-stop-daemon: did not create a valid pid in `/var/run/transmission/transmission.pid'                                                              [ !! ]
 * ERROR: transmission-daemon failed to start

Now, status of the service is set as stopped although transmission-daemon starts and the pid files is created.

I'll attach suggested change to the init script that makes transmission-daemon app run in the foreground and tell start-stop-daemon to do this job.

Reproducible: Always

[Comment 1 Sławomir Nizio 2012-02-13 18:31:56 UTC]

Created attachment 301793 [details, diff]
patch for $FILESDIR/transmission-daemon.initd.8

[Comment 2 Xake 2012-02-22 08:53:09 UTC]

I would like to know why this breaks for you but work so fine for me.

[Comment 3 Sławomir Nizio 2012-02-22 17:51:02 UTC]

Here comes the answer:

your comment made me to search for similar issues. This bug and particular comment was helpful:

https://bugs.gentoo.org/show_bug.cgi?id=368285#c6

- now I remember I'd changed rc_start_wait in /etc/rc.conf, and while the value of 20 ms was good enough for every other service, that's not the case with transmission. I forgot about it.

According to comments in the linked bug report, mainly 11th, I'm also closing this one.
So in short, problem was only with my settings. Augh.

PS OpenRC is 0.9.8.1