New Transmission add-on thread

[super-poussin]

Try disable Lpd, utp and pex

[ikkieman]

Hey guys,
I'm new to the entire NAS-world and also new to this forum, but it's been a super help so far.
About 4 weeks ago I bought my NV+ V1 and I've got time machine backups working, installed a few drives and made sure I could see it's stats, and used ReadyNAS Remote to make sure I could get to my files anywhere. These seem to be running quite smoothly. But I seem to have some problems with Transmission 2.42 on Raidiator 4.1.9. The service seems to die every time. What happens is that
1. I start up the NAS
2. I start up Transmission
3. After a few minutes the WebUI seems to die and Transmission seems to crash. I get the message that it's "Connection Failed. Could not connect to the server. You may need to reload the page to reconnect."
4. The green statusblob turns grey in the frontview and I can restart Transmission, but it repeats over and over and over.

Now, I've reviewed the status of my NAS. It has the original 256 MB of RAM in it and it typically has about 4 MB of free memory. Could this have anything to do with it? If so, i'm buying a new plate of RAM and fixing it.
If not, what can I do? I've changed nothing to the .json file except the max share ratio (set it to 3) and changed true to false on the maximum upload speed.
Do you have any tips, keeping in mind that I don't know the first thing about SSH-ing?

[sjw]

I think there's a memory leak somewhere. I thought exactly the same as you - there's 4000k or so available.. I put a 1GB stick in a week ago hoping it would make a difference (I have a 30b, soon to be 60Mb connection) but it didn't. Rarely get speeds above 2MB/s and RAM steadily goes down and ends up the same..

[ikkieman]

Over here it's not the speed that bothers me. The internet connection works fine. I get the max up and down on my connection, no problem. It's just that I'm getting sick and tired with transmission crashing on me every few minutes.

[btaroli]

... I seem to have some problems with Transmission 2.42 on Raidiator 4.1.9. The service seems to die every time. ... what can I do? I've changed nothing to the .json file except the max share ratio (set it to 3) and changed true to false on the maximum upload speed.

Well, a few thoughts come to mind:

• 4.1.9 has apparently at least one nasty issue regarding share permissions. I wonder if it's possible that file permissions could be affecting Transmission's ability to access files and it results in crash. See http://www.readynas.com/forum/viewtopic.php?f=17&t=64230. You might want to consider using 4.1.8 instead.
• I don't recall off the top whether Transmission offers a log where debugging info can be captured, but might want to consider doing that to review.
• Though it's often useful to stay on the latest release, you might try going back a version or two and see if you get better behavior.

FWIW, modifying the settings.json shouldn't require ssh access. More recent editions create an addons-config share that you can mount (may require "admin" user) as CIFS or AFP and edit the file that way. Just make sure that Transmission isn't running when you do that. It overwrites the file with current configuration when it shuts down.

[ikkieman]

Btaroli, that's true. Since my NV+ V1 has the stock RAM installed, a cache file of 100 MB is a bit too much. I've crancked it down to these specs (http://www.readynas.com/forum/viewtopic.php?f=36&t=61555) as a guideline. Has been running for a few hours now and works fine since. It's even downloading every James Bond movie right now without a hickup. Thanks for everything with the fast responses guys. And actually I'm a bit amazed that the NV+ V1 is still supported by Netgear. I've seen companies that 'discard' support after only 4 years. Liking this!
Not to be mean or be anoying or anything, but throwing in a 100 MB cache file on a device which has 256 MB of RAM standard?
Not to say that I'm capable of doing a better job, but yeah... Just my thoughts.

[gibxxi]

The add-on won't start automatically from a cold-start on x86 (so this may also be the case for SPARC), so be aware of this when you re-start your NAS, that you *may* need to start transmission manually. Also, if you haven't already done so, set up the start.sh, stop.sh, and blocklist.sh to have the same password / username config you specified in settings.json. All the files are in the same folder if memory serves.

Finally, I wouldn't openly discuss the nature of what your downloading on these forums if I were you.

[MysteryMan]

I have a ReadyNAS Duo, which is running Transmission 2.42 and I was planning download a torrent from PirateBay. However, I see that now they are using these Magnets rather than .torrent files.

Before I expend too much energy can someone tell me if it should be possible to get the Transmission add-on to use Magnets?

[MysteryMan]

Right, sorted it! Downloaded and installed Remote Transmission GUI and this seems to have done the trick

[Mr_B]

Ah, yes. "Any" management software will pass the magnet links properly to transmission. Also, copy the magnet link, and paste it in the URL text-box in "open", within the web-interface works. Sorry for the late reply ;- )
B!

[MysteryMan]

The add-on won't start automatically from a cold-start on x86 (so this may also be the case for SPARC), so be aware of this when you re-start your NAS, that you *may* need to start transmission manually. Also, if you haven't already done so, set up the start.sh, stop.sh, and blocklist.sh to have the same password / username config you specified in settings.json. All the files are in the same folder if memory serves.

Finally, I wouldn't openly discuss the nature of what your downloading on these forums if I were you.

Sorry to be pedantic, but, I just want to be sure I understand what you are saying.

Until yesterday, I had an older version of Transmission running on my ReadyNAS Duo. I use the power options on the NAS to switch off at night and back on in the morning. Transmission would be there whenever I needed it.

Are you saying that it is likely that the latest Transmission will not restart when the NAS boots up in the morning now and that I will have to manually start it? It does seem that Transmission is not running this morning! I have stopped it and it is in the process of starting again - although it does seem to be taking forever!

This is a real bummer if true!!!!!

[Mr_B]

I can only say as much, the first time i installed 2.42, it worked just fine, then i tested a beta, and finally reinstalled 2.42. After which the darn thing no longer automatically starts on boot. I'm assuming it's something in the startup process rather then transmission itself that has been messed up.
My attempt at fixxing it, will someday be emptying the raid, and running a factory reset, and reinstall transmission. If it will work, no idea, but since i "never" restart my unit, i haven't made it a priority.
B!

[MysteryMan]

Thanks for reply.

I have installed an old version of Transmission (2.22) and this seems to work OK. Well, it has downloaded a torrent for me. I'll see what happens tomorrow morning!!!!

[absincog]

I previously had Transmission 2.60.02 working perfectly on an NVX. I had installed the add-on several years ago and had upgraded through new versions with no issues.

I just re-installed v2.60.02 after "factory resetting" and rebuilding my NVX (not by choice; volume went bad in an unrecoverable sort of way). I am running the latest firmware (4.2.21). When I try to enable Transmission after installing it, I receive the following message, "Transmission service failed to start." I have not made any changes to the settings.json file.

Can someone point me in a direction to troubleshoot this?

[Mr_B]

If possible, factory reset, and reinstall. Possibly uninstalling and reinstalling will work too, but that means you have to be able to run the uninstall script manually.
B!