Closed GoogleCodeExporter closed 9 years ago
It was a fairly well known issue that the Transmission RPC becomes unresponsive
when there's lots of disk activity, this will be especially the case on a NAS
which doesn't have a great deal of CPU power. I don't know if this has improved
or not.. It happens less to me these days but maybe that's due to a more
powerful machine. But as you say, if the web interface works then this probably
should do.
Did you know the timeout and number of retries? What are both currently set to?
You probably need to increase these.
To debug this (for Windows) I'd suggest using a HTTP debugger, like fiddler
(http://www.fiddler2.com/fiddler2/). transmission-remote-gtk should use the
proxy settings from IE on Windows.
Original comment by a...@eth0.org.uk
on 5 Aug 2012 at 9:30
Thanks for letting me know it is a known issue.
I know the number or retires is three, but have no idea about the timeout time
value.
I will check in IE and see what I can easily find.
Not sure if I will have time to play with fiddler, but Thanks for letting me
know about it.
Original comment by snoopy.p...@gmail.com
on 5 Aug 2012 at 2:10
Original comment by a...@eth0.org.uk
on 10 Aug 2012 at 12:10
got the same issue
remote-gtk on my workplace's Ubuntu connects to my home transmission daemon
(even remote preference become available) but always got timeout errors after
that. other remotes works fine (webui, Transmission-remote-gui,
Transmission-remote-dotnet, Transdroid etc)
daemon 2.22 running on my home server
Original comment by jetpr...@gmail.com
on 26 Nov 2012 at 12:01
Original issue reported on code.google.com by
snoopy.p...@gmail.com
on 5 Aug 2012 at 1:44