Hi,I am having an issue where the Tranismission service seems to constantly become inactive. I.e. The active "LED" is grey (not green.)I am running Transmission 2.42 and RAIDiator 4.1.8.I have to manually start Transmission and the time between it becoming active and inactive is generally only a few minutes. The Tranmission web interface also shows the error "Could not connect to the server. You may need to reload the page to reconnect."This has happened with the previous version of RAIDiator and previous versions of Transmission, so I am not sure what the problem is. Any help would be greatly appreciated.Thanks!

I have the exact same issue. Short descrition. I have used the transmission BT client for some time and it hae worked fine until a few days ago. I am pretty sure it has someting to do with the radiator upgrade to 4.1.8 (I tried the 4.1.8 T9 today -same issue ) i did a ferw days ago. Now, the transmission client will work for awhile, then go offline. The green dot that indicates that it is up and going in the web gui of the ready duo goes grey. If oi restart it, it will work for alittle while again, then just go offline. So far i have tried the newest 2.42 and currently trying the 2.31 version. I also tried the light version, and that actually worked. But the light version wont seed - so i cant really use that version either. Just for error searching, i made no changes at all in the settings.json file. I get no diffrent result from that vs when i make the usual changes. Password and a few other options. The port is working fine and responding as it should in the router, and when it is online, it both downloads and seeds. Let me know if you have any suggestions on this, or want more info concerning it. I have seen more people having the same issue to, but no answers or suggestions to how to solve this...

I am currently in the process of moving my data to a second device with the thought of resetting my device to factory settings. I have tried everything I can think of to get it to work, without any luck.Any advice from someone who knows how to resolve this issue would be much appreciated!

same issue here too on duo 4.1.8 and latest transmission.

Same issue here too on Readynas Duo 4.1.8 and 2.42 transmission

same think with me !! i have the readynas duo 4.1.8 and the transmission keeps dieing.. when it starts downloading it's all good about 10 min then suddently the bandwith falls to 0 kb/s and after will i can't even contact with the page of trasmission thru safari !! i did a small reaserch and i found some post's there where sayin'g that you have to change the permissions to the usage of cpu and stuff tha you have to be atlist a programer or nowing command line on unix. If someone now's a more simple way to fix this problem will be very helpfull !!!

Transmission constantly turns inactive

53 Replies

Replies have been turned off for this discussion

simcat
Aspirant
Nov 17, 2012
Just bought my NV+. After fresh installation of Transmission 2.42 tried some torrents and crashed >5 times before I had downloaded 4 gig. After I changed cache size it downloaded 8 gig so far without crashing.
RAIDiator 4.1.10 with Transmission 2.42.
sendjes
Aspirant
Nov 17, 2012
Using RAIDiator 4.1.10 with Transmission 2.42 I just tested the change in MB's, and it truly works, so far no crashes of any kind, will leave for a few days and see.

gasmanpopey

Aspirant

Mar 29, 2013

This has just fixed mine too - great find.

I'm running radiator 4.2.21 on a ReadynasPro4 and this has been annoying me for ages. Finally got round to putting transmission 2.77.01 on, hoping that it would fix the problem but if anything it got worse.

Just checked the cache setting and it was 2048!?! I've set it to 8 and all appears to be well now. I wonder where these ridiculous cache sizes are coming from? I can't imagine the dev is setting them that way, given that (so far as I know) none of the product range come with >2GB of ram.

And the Transmission website had this to say for the latest release so it not come from there ether.

cache-size-mb: Size (default = 4), in megabytes, to allocate for Transmission's memory cache. The cache is used to help batch disk IO together, so increasing the cache size can be used to reduce the number of disk reads and writes. Default is 2 if configured with --enable-lightweight.

I wonder if a rogue update has made a mess of the config at some point.

Forum Discussion

Transmission constantly turns inactive

53 Replies

Related Content

Armor showing inactive subscription

ReadyNAS RN424 | Inactive Volume + RAID Issue

Orbi 970 constantly drops wifi to devices

AX12 RAX120 Constantly Rebooting

Re: DHCP constantly renewing XR500

NETGEAR Academy

ProSupport for Business