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
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
Hi
On Mon, Jul 15, 2013 at 7:25 PM, Suvayu Ali fatkasuvayu+linux@gmail.comwrote:
Hi,
I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:
# systemctl start transmission-daemon.service
Make sure you have https://admin.fedoraproject.org/updates/FEDORA-2013-13033/transmission-2.80-....
Rahul
On 07/16/13 10:37, Rahul Sundaram wrote:
Hi
On Mon, Jul 15, 2013 at 7:25 PM, Suvayu Ali <fatkasuvayu+linux@gmail.com mailto:fatkasuvayu+linux@gmail.com> wrote:
Hi, I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs: # systemctl start transmission-daemon.service
Make sure you have https://admin.fedoraproject.org/updates/FEDORA-2013-13033/transmission-2.80-....
Yes....
yum --enablerepo updates-testing update transmission*
will fix it.....
Hi Rahul,
On Tue, Jul 16, 2013 at 11:14:29AM +0800, Ed Greshko wrote:
On 07/16/13 10:37, Rahul Sundaram wrote:
On Mon, Jul 15, 2013 at 7:25 PM, Suvayu Ali <fatkasuvayu+linux@gmail.com mailto:fatkasuvayu+linux@gmail.com> wrote:
I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs: # systemctl start transmission-daemon.service
Make sure you have https://admin.fedoraproject.org/updates/FEDORA-2013-13033/transmission-2.80-....
Yes....
yum --enablerepo updates-testing update transmission*
will fix it.....
Thank you! I was looking at bug #984220[1], but missed the -2 in the version; I had 2.80-1. Updating from updates-testing, fixed my problem.
That said, now transmission-remote-cli does not work (incompatible protocol versions). I believe there is a new version of transmission-remote-cli[2] that supports the change[3].
Footnotes:
[1] https://bugzilla.redhat.com/show_bug.cgi?id=984220
[2] https://bugzilla.redhat.com/show_bug.cgi?id=798970
[3] https://github.com/fagga/transmission-remote-cli/blob/master/NEWS#L16
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,
Hi
On Tue, Jul 16, 2013 at 4:33 AM, Suvayu Ali wrote:
Hi Rahul,
That said, now transmission-remote-cli does not work (incompatible protocol versions). I believe there is a new version of transmission-remote-cli[2] that supports the change[3].http://fedoraproject.org/wiki/Mailing_list_guidelines
I have requested a push of the latest version of transmission-remote-cli for Fedora 19 and will let the maintainer handle that. If it doesn't happen soon, let me know and I can commit as a provenpackager.
Rahul
On Tue, Jul 16, 2013 at 10:01:31AM -0400, Rahul Sundaram wrote:
On Tue, Jul 16, 2013 at 4:33 AM, Suvayu Ali wrote:
That said, now transmission-remote-cli does not work (incompatible protocol versions). I believe there is a new version of transmission-remote-cli[2] that supports the change[3].http://fedoraproject.org/wiki/Mailing_list_guidelines
I have requested a push of the latest version of transmission-remote-cli for Fedora 19 and will let the maintainer handle that. If it doesn't happen soon, let me know and I can commit as a provenpackager.
Thanks a lot Rahul.
Hi Rahul,
On Tue, Jul 16, 2013 at 06:00:48PM +0200, Suvayu Ali wrote:
On Tue, Jul 16, 2013 at 10:01:31AM -0400, Rahul Sundaram wrote:
On Tue, Jul 16, 2013 at 4:33 AM, Suvayu Ali wrote:
That said, now transmission-remote-cli does not work (incompatible protocol versions). I believe there is a new version of transmission-remote-cli[2] that supports the change[3].
I have requested a push of the latest version of transmission-remote-cli for Fedora 19 and will let the maintainer handle that. If it doesn't happen soon, let me know and I can commit as a provenpackager.
Thanks a lot Rahul.
I hate to bother you again; I tried updating transmission-remote-cli with updates-testing enabled, but there seems to be no update. I checked BZ #798970, there seems to be no status updates there either.
Any news?