Transmission constantly turns inactive

BikeHelmet wrote:

noilly wrote: 3. Navigate to and open the settings.json file (..\addons-config\Transmission\transmission-daemon\). Notice that on the fresh install of v2.42, the settings.json file has a value cache-size-mb = 200 4. Change cache-size-mb to cache-size-mb = 2 Is the default value in 2.42 so high? I found any value above ~20 caused stability issues in past versions. I think I had mine set to 8MB to cut out a bit of I/O without gobbling all the RAM.

200 was the default value!

Thanks noilly, just made the change will let you know how it goes.

If anyone knows how to stop/start the transmission service from ssh that would be awesome to know.

Hi,

Well after a very frustrating day repeatedly installing/uninstalling Transmission, rebooting my NV+, changing security mode between "Share" and "User", modifying JSON settings, ... (you get the picture) ... I thought I'd finally got everything working. I added a couple of Torrents and all looked good.

However, I've found my way here as I now have the issue where Transmission becomes inactive after a few seconds. I've tried the change suggested above but this doesn't appear to work for me.

At one point I tried to admit defeat and remove Transmission altogether - but it wouldn't uninstall. Software that behaves like this makes me very nervous.

Any other ideas guys?

Thanks in advance,
Ian.

ReadyNas NV+
RAIDiator 4.1.8
Transmission 2.42

Hello, I can confirm that above fix appears to work for:

ReadyNAS Duo (sparc version)
Raidiator 4.1.8.
Transmission 2.42.

I've changed the memory in "settings.json" from 200 to 8. I might later increase to about 20 (it appears that I have 190 free right now).

I've had two concurrent downloads for the last 30 minutes with combined download speed of 1.5 Mb/s.

Previously, Transmission would crap out after 5-6 minutes. So, this is a new record. Hopefully, it continues to work.

Note: I am accessing Transmission GUI from my LAN. I don't know how it will behave once I try to access from work.

Note 2: I don't know how to start it up from command line? /etc/rc3.d/ has no reference to Transmission client. If anyone figured this out, please share.

milanm wrote:
Note 2: I don't know how to start it up from command line? /etc/rc3.d/ has no reference to Transmission client. If anyone figured this out, please share.

I'm very curious about that as well. I'm not sure what actually starts the daemon. I looked around, but my lack of familiarity with older linux distros hasn't helped me any.

Something I've wondered about - is the cache size per-active-torrent or total? Because 200MB per active torrent would be way too much memory. 8MB total seems low, but being set to 8MB seems to work well.

Okay, I've had another go with this today - yet another uninstall/reinstall, change JSON settings file (I set cache size to 8) and Transmission has been up and running for a good few hours now. Fingers crossed this has fixed it!

Ian.

noilly wrote:

BikeHelmet wrote: noilly wrote: 3. Navigate to and open the settings.json file (..\addons-config\Transmission\transmission-daemon\). Notice that on the fresh install of v2.42, the settings.json file has a value cache-size-mb = 200 4. Change cache-size-mb to cache-size-mb = 2 Is the default value in 2.42 so high? I found any value above ~20 caused stability issues in past versions. I think I had mine set to 8MB to cut out a bit of I/O without gobbling all the RAM. 200 was the default value!

Not sure why it is so high considering transmission default is 4

I am still running 2.33, which also had cache-size-mb set to 200 which I have changed to 8, so it will be interesting to hear if it stops 2.42 from constantly crashing

michelefaccini wrote:
I had the same problem which I solved using Transmission Remote GUI ( see http://code.google.com/p/transmisson-remote-gui ).The interface is not complete as the uTorrent one but anyway it works...When I will have enough time, I will try installing uTorrent which is The One for peer to peer.....

Hi there any one get this to work?
Is there any permissions i need to solve?
in Connection...
Remote host : my nas name or ip
port: the port for Transmission or webgui port?
User name: admin
Password: password1 (its the default password for transmission)

I get timed out all the time...

I use Transmission Remote Dotnet, aim it at the NAS IP, port 8181, user / pass admin / password1. (Well, i changed my password, but thats the default one)
I'm guessing your hitting the wrong ip, and / or port, best of luck.
B!

Mr_B wrote:
I use Transmission Remote Dotnet, aim it at the NAS IP, port 8181, user / pass admin / password1. (Well, i changed my password, but thats the default one) I'm guessing your hitting the wrong ip, and / or port, best of luck. B!

AAA 8181 did the trik had it set to 8080
Thanks m8