Transmission constantly turns inactive

No worries, happy to be able to help someone for a change. Usually it's me needing someone to hold my hand, and walk me through it.
B!

noilly wrote:

Steps I took to solve issue: 1. Install latest version of Transmission (2.42) 2. Stop the Transmission service 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 5. Save the file 6. Restart the Transmission service

Fabulous! This seems to have resolved Transimissions' problems for me.

Thank you noilly!

The "cache-size-mb =" at 2 seems to have cleared this problem for me. It had become such a nuisance that I downgraded Transmission to 2.22 a year ago. No problems with it to speak of, though the browser interface was, at times, a bit sluggish.

Before upgrading back to 2.42 I checked the cache-size in the settings.json file and, sure enough, it was set to 2. Apparently that was the default size for ver. 2.22, because I'd never changed anything in settings.json until today.

UPDATE: I spoke too soon. After re-adding some torrents it started disconnecting again. VERY frustrating. I really like the new features since 2.31, but they're of no value if it's constantly disconnecting. I'm back to 2.22.

Doesn't anyone have a way of fixing this problem?

BTW: I'm running 1GB of memory (and yes, my memory tests out just fine).

noilly wrote:

Hi All, I have solved my problem! After months of my Transmission turning off every few minutes, it has now been running for over three hours straight downloading multiple torrents. Steps I took to solve issue: 1. Install latest version of Transmission (2.42) 2. Stop the Transmission service 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 5. Save the file 6. Restart the Transmission service Happy torrenting! I would love to know if this works for others, so please post if the above steps solved your issues too!

Seems to have worked for me....a bit of time will tell.... Running 2.42 on 4.1.10 T3
Will update after a few days
Fingers crossed!!!!
:D


Been a few hours now, and still fine, completed 7 or so torrents.....

Now been several days and I've had no issues, on the odd occasion if I leave the web page open I get a disconnected error, but just refresh the page and it's fine!

Seems to have worked for me also :D

I find my DL/UL speeds are alot lower since 4.1.9, and as well with 4.1.10 T3, I have had my Cache set to 2mb since 4.1.9 T2. I used to see 1.5-2m down and 200-300k k up.... since the 4.1.9 update i typically dont break 1mb down and seem to be around 75k up average..... Also tried 4.1.10 T3 with no improvment!!

I'have the same promblem, I think, the service stop after one o r two hours and I must restart he service anytime, I try your solution and i see if work.
I hope, Thank you

Ok, it work, thank you very much

Hi,

After the proposed modification, transmission seems to remain active but uses around 95% CPU when downloading.

I've never checked the CPU usage of earlier versions of Transmission (combined with earlier versions of RAIDiator) but isn't that a lot???

Anyone else experiencing the same high CPU usage?

Thanks,

Harck