New Transmission add-on thread

If your installing over a previous version, you will need to edit the transtart.sh, transtop.sh and blocklist.sh files in the addons-config/Transmission folder/share. By default, the password for the admin user is set to password1. If you've changed that password for the admin user, the corresponsing entries in the files listed above need to also be edited to match your new password. This ought to fix both the "Transmission Service Failed To Start" message (even though it DOES start) and/or a constantly spinning progress icon.

You will need to edit these files while the service is stopped, or after the upgrade, but prior to first activation.

Has anyone had the same experience with 4.1.9 and Transmission 2.42?

I had to re-install Transmission to get it to work. Works like a charm, as always, after that.

Same here - had to uninstall and re-install. Seems OK....

Hey i have been useing Transmission for some time now without problems but when i try to download a big torrent it hangs and some times even crashes im useing Transmission 2.42 on a ReadyNas duo the file im trying to download is 3xxgb big and its only a part of it like 50gb what can i do to make it work?

My Settings:
{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"blocklist-url": "http://list.iblocklist.com/?list=bt_level1",
"cache-size-mb": 8,
"dht-enabled": true,
"download-dir": "/media/BitTorrent/",
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 2,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/c/media/BitTorrent/Incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": true,
"max-peers-global": 120,
"message-level": 3,
"open-file-limit": 32,
"peer-congestion-algorithm": "",
"peer-limit-global": 100,
"peer-limit-per-torrent": 30,
"peer-port": 6881,
"peer-port-random-enabled": 0,
"peer-port-random-high": 65535,
"peer-port-random-low": 1024,
"peer-port-random-on-start": false,
"peer-socket-tos": "default",
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"prefetch-enabled": 0,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"queue-stalled-enabled": false,
"queue-stalled-minutes": 30,
"ratio-limit": 2,
"ratio-limit-enabled": false,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{d15b146a3063b3ade7d0fecaa9602218a327a8c8gOoal64v",
"rpc-port": 8181,
"rpc-url": "/transmission/",
"rpc-username": "admin",
"rpc-whitelist": "*",
"rpc-whitelist-enabled": true,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"seed-queue-enabled": false,
"seed-queue-size": 5,
"speed-limit-down": 400,
"speed-limit-down-enabled": false,
"speed-limit-up": 20,
"speed-limit-up-enabled": false,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 18,
"upload-slots-per-torrent": 3,
"utp-enabled": true,
"watch-dir": "/c/media/BitTorrent/sources/",
"watch-dir-enabled": 0
}

Try disable Lpd, utp and pex

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?

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

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.

ikkieman wrote:
... 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. :)

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.