Transmission constantly turns inactive

Same issue with me.

When I connect with root SSH, and do a "top" command, I see that Transmission is using a lot of CPU.

My feeling is that, there is a resource issue with Raidiator 4.1.8, creating an higher CPU usage and hence, less resource for other processes.

If for one reason or another the CPU is heavy loaded, Transmission crashes and can even crash the whole Readynas.

But not only, a BIG TimeMachine backup (500 Gigs) creates the same effect: crash of the Readynas which then needs a cold reboot.

For Transmission, I'll try to limit the download speed so that the CPU usage is "acceptable", until a firmware solution comes up and revert to 4.1.7.

@mcroger I agree I've been looking at the CPU useage with the "top" command is it's almost 100% most of the time.
how do you limit CPU useage ?

The only parameters on which I can play (as a regular user, not a real hacker who can dig further in the system) are the dld/upld speeds and the quantity of active torrents.

There must be a better solution than mentioned above. These are temporary solutions and don't allow you to take full advantage of the device or Transmission. Does anyone know if this issue is being looked at by Netgear or Transmission?

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.....

I am having the same problem as everyone else here with transmission going inactive. It also seems only to have started since the new radiator update.

Runing radiator 4.1.8
Tansmission 2.42

anyone seen any solutoins to this?

mcroger wrote:

Same issue with me. When I connect with root SSH, and do a "top" command, I see that Transmission is using a lot of CPU. My feeling is that, there is a resource issue with Raidiator 4.1.8, creating an higher CPU usage and hence, less resource for other processes. If for one reason or another the CPU is heavy loaded, Transmission crashes and can even crash the whole Readynas. But not only, a BIG TimeMachine backup (500 Gigs) creates the same effect: crash of the Readynas which then needs a cold reboot. For Transmission, I'll try to limit the download speed so that the CPU usage is "acceptable", until a firmware solution comes up and revert to 4.1.7.

Here's some more info for everyone in this thread.

I was having issues where Transmission (v2.x.x to 2.3.x by super-poussin) was crashing my ReadyNAS NV+ 4.1.7 in record time. Usually 5 mins to a couple hours when downloading and perhaps as long as half a day when seeding.

I noted that if I rebooted my ReadyNAS it took longer for Transmission to crash. Sometimes if I couldn't even get it to start, rebooting would get it to start and run for hours. Reducing the number of torrents seemed to help, but even with low numbers of torrents stability was an issue.

I bought some memory and did a RAM upgrade. That got it somewhat stable, often taking nearly two days to crash. Once or twice it got close to half a week. And when it dropped down to merely hours, I'd just reboot my NAS to reset it.

Eventually, when 4.1.8 came out, I chose to not upgrade. I wanted to see what the verdict was first. Then the day Transmission 2.4.2 came out, I jumped on that.

Transmission 2.4.2 on 4.1.7 has been perfectly stable - even with large numbers of torrents. I was seeding well over 1000 for a couple months without crashes. I seeded all the Humble Indy Bundle downloads for a while. :D And tons of stuff off Vodo. Meanwhile I was also downloading dozens of torrents, etc., with no crashes. It has not crashed once yet.

The new UI is different - it responds quicker, but lacks filesize info on your torrents. I don't like the look as much, but I do like the capabilities, speed, and stability.

To everyone having issues with 2.4.2... it's possible that 4.1.8 is causing it. Well, that or some other piece of the puzzle is different. (like no RAM upgrade)

So with the info above does anyone know of any problems with down grading to the earlier firmware?

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".

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.