On Tue, Jul 16, 2013 at 07:52:33AM +0800, Ed Greshko wrote:
On 07/16/13 07:25, Suvayu Ali wrote:
Hi,
I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:
# systemctl start transmission-daemon.service
If I let it be for a few minutes (~5), it finishes with a failure. The log is extremely unhelpful. This is very strange because it was working just fine until a few days ago.
Jul 16 01:20:00 <hostname> systemd[1]: Starting Transmission BitTorrent Daemon... -- Subject: Unit transmission-daemon.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
To fix this....
yum downgrade transmission-daemon
And, file a bugzilla please....
I don't used this service....but I notice the systemd service file has changed from...
ExecStart=/usr/bin/transmission-daemon -f --blocklist -g /var/lib/transmission/.conf ig/transmission
to
ExecStart=/usr/bin/transmission-daemon -f --log-error
I think that is deliberate. See comment 4 and 5 here: https://bugzilla.redhat.com/show_bug.cgi?id=984220
BTW, how does one override the ExecStart= line in a service file without creating one in /etc/systemd/system/? I was trying it because of the above change and finally gave up and moved my configuration to the default location.
I was trying to override it by putting my service file in /etc/systemd/system/<unit>.service.d/myfile.conf (<unit> is transmission-daemon of course). Simply repeating the line does not work. Systemd refuses by saying cannot have multiple ExecStart= lines. Then I came across the following syntax in a bug report (forgot the number):
ExecStart= ExecStart=<new_command>
But using that in my conf file doesn't seem to work either.
Actually now I'm thinking maybe the service file worked, but transmission failed because without the fix in 2.80-2.
Cheers,