Transmission constantly turns inactive

same problems here, it stops, annoying.. "NETGEAR, Connect with nothing" at this rate.

Hello,

To may be help Super Poussin to solve the problem i've logs :

Firstly i've this one

Nov 21 20:27:23 readynasduo transmission-daemon[20094]: TorrentName Piece 471, which was just downloaded, failed its checksum test (peer-mgr.c:1791)

And after few minutes :

Nov 21 20:40:45 readynasduo kernel: oom-killer: gfp_mask=0x200d2, order=0 Nov 21 20:40:45 readynasduo kernel: [8006698c : read_swap_cache_async+0xb8/0xd8 ] [8005e724 : do_swap_page+0x3d4/0x48c ] [8005f084 : __handle_mm_fault+0x154/0x4a4 ] [803410f4 : 0x803410f4 ] [80340110 : 0x80340110 ] [00001009 : 0x1009 ] Nov 21 20:40:45 readynasduo kernel: Mem-info: Nov 21 20:40:45 readynasduo kernel: DMA per-cpu: Nov 21 20:40:45 readynasduo kernel: cpu 0 hot: high 0, batch 1 used:0 Nov 21 20:40:45 readynasduo kernel: cpu 0 cold: high 0, batch 1 used:0 Nov 21 20:40:45 readynasduo kernel: DMA32 per-cpu: empty Nov 21 20:40:45 readynasduo kernel: Normal per-cpu: Nov 21 20:40:45 readynasduo kernel: cpu 0 hot: high 18, batch 3 used:1 Nov 21 20:40:45 readynasduo kernel: cpu 0 cold: high 6, batch 1 used:5 Nov 21 20:40:45 readynasduo kernel: HighMem per-cpu: empty Nov 21 20:40:45 readynasduo kernel: Free pages: 3920kB (0kB HighMem) Nov 21 20:40:45 readynasduo kernel: Active:13593 inactive:317 dirty:0 writeback:0 unstable:0 free:245 slab:636 mapped:13353 pagetables:0 Nov 21 20:40:46 readynasduo kernel: DMA free:1168kB min:112kB low:128kB high:160kB active:0kB inactive:0kB present:16384kB pages_scanned:0 all_unreclaimable? yes Nov 21 20:40:46 readynasduo kernel: lowmem_reserve[]: 0 0 60 60 Nov 21 20:40:46 readynasduo kernel: DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no Nov 21 20:40:46 readynasduo kernel: lowmem_reserve[]: 0 0 60 60 Nov 21 20:40:46 readynasduo kernel: Normal free:2752kB min:1840kB low:2288kB high:2752kB active:217488kB inactive:5072kB present:245760kB pages_scanned:13303 all_unreclaimable? no Nov 21 20:40:46 readynasduo kernel: lowmem_reserve[]: 0 0 0 0 Nov 21 20:40:46 readynasduo kernel: HighMem free:0kB min:512kB low:512kB high:512kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no Nov 21 20:40:46 readynasduo kernel: lowmem_reserve[]: 0 0 0 0 Nov 21 20:40:46 readynasduo kernel: DMA: 1*16kB 0*32kB 0*64kB 1*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB = 1168kB Nov 21 20:40:46 readynasduo kernel: DMA32: empty Nov 21 20:40:46 readynasduo kernel: Normal: 58*16kB 7*32kB 5*64kB 2*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB = 2752kB Nov 21 20:40:46 readynasduo kernel: HighMem: empty Nov 21 20:40:46 readynasduo kernel: Swap cache: add 431022, delete 428371, find 59611/128573, race 2+0 Nov 21 20:40:46 readynasduo kernel: Free swap = 40272kB Nov 21 20:40:46 readynasduo kernel: Total swap = 255968kB Nov 21 20:40:46 readynasduo kernel: Free swap: 40272kB Nov 21 20:40:46 readynasduo kernel: 14141 pages of RAM Nov 21 20:40:46 readynasduo kernel: 245 free pages Nov 21 20:40:46 readynasduo kernel: Out of Memory: Kill process 20094 (transmission-da) score 43412 and children. Nov 21 20:40:46 readynasduo kernel: Out of memory: Killed process 20094 (transmission-da). Nov 21 20:40:46 readynasduo kernel: Out of memory: Killed process 20095 (transmission-da). Nov 21 20:40:46 readynasduo kernel: Out of memory: Killed process 20096 (transmission-da). Nov 21 20:40:46 readynasduo kernel: Out of memory: Killed process 20097 (transmission-da).

Kind regards

Having to use the pre-installed BitTorrent add-on whilst this is sorted :(

OK so I thought it was the password error but it's not. Thinking of just buying more ram for my box.
God this is seriously annoying me now! :-(

Now done a memory upgrade and it seems to be stable again.

Wizball wrote:

BikeHelmet wrote: Wizball wrote: So with the info above does anyone know of any problems with down grading to the earlier firmware? Problems? I think downgrading requires a factory reset, so you need a backup of all your data? That's the main "problem". OK down graded my ready nas NV+ it does not have a memory upgrade and transmission is still stopping. I will have to work out what has changed as it never use to.

Wizball wrote:
Now done a memory upgrade and it seems to be stable again.

What do you have? NV or Duo?
I have a Duo and I think I'll just buy 1gb of ram for it to try. Otherwise I'm binning this and buying a qnap box. Seriously sucks, I wish I never upgraded to the latest firmware.
I can only think of resetting the box by pulling out a drive, resetting it to factory defaults (would that get me back to factory firmware also? ) then putting my other drive in a caddy and transferring all the data back to the nas again, which would take so long.

This has got to be permissions problem surely. Something is hanging and not timing out?

Does anyone have an easier way to go back a firmware upgrade?

I have an nv.
Just download the old firmware and used that to update.

I'm getting the same problem.

Transmisison 2.42, RAIDiator 4.1.8.

top from SSH shows:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
21422 nobody 33 18 236m 142m 3952 R 6.9 64.6 8:35.64 transmission-da

With only 1 torrent going. I've tried a fresh install of Transmission with no luck.

Would a RAM upgrade help? Is it possible to restart transmission-daemon via SSH?

thanks

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!

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.