New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)

Just had my settings.json file corrupt itself for no apparent reason. Couldn't get to the web interface, and in Frontview it said the service was started/running but the green light was greyed out.

Renamed the corrupt settings.json (couldn't even open the file to edit it), restarted the service so it would generate a new default , then stopped it again to tweak the settings to how I like them.


Everything had been working fine for the last month or two since I got rid of the old 2.42 by Super-Poussin(sp?) and updated to Tarobun's 2.84, so no idea how/why this happened. No power cuts, drive problems, or NAS locking up. Just thought I'd note it here just in case someone else runs into the problem.

Oh, seeing as I was messing around in Frontview anyway I updated to the latest RAIDiator 4.1.14 firmware after fixing Transmission, so far no dramas with the update as far as I can tell. I don't use the watch-dir so no idea about emk's problem, sorry.

emk wrote:
Anyone else having watch-dir issues with 2.84? Seems any torrent files dropped in my watch-dir aren't being loaded. Was working on 2.83 and earlier.

Took me for ever to get around to this. Sorry. I just tested it on my system. Had to configure a watch dir, and such since i wasn't using one. But after that it was working as a charm. You might want to double check so you got:

"watch-dir": "where ever"
"watch-dir-enabled": true

in your settings.
B!

Ii appears I got it working after testing a few things. Firstly, I tried changing "watch-dir-enabled": the value has always 1, not true. So I tried playing around with this, but the true/false value definitely doesn't work for me. Only binary 0 or 1 work.

Secondly it appeared to be a permission problem, depending on which machine I drop the file from or how I connect to the share (e.g.: sometimes I drop directly from either mac/PC at home, sometimes I drop it when I VPN in from remote location. Sometimes I even SCP the file over). I also restarted my box to flush any gremlins out, good old Windoze fix never hurt anyone right :D

emk wrote:
Ii appears I got it working after testing a few things. Firstly, I tried changing "watch-dir-enabled": the value has always 1, not true. So I tried playing around with this, but the true/false value definitely doesn't work for me. Only binary 0 or 1 work.

I copied the variables from my settings.json after i set it up so it was working. If you got a different need in your settings.json, then your most likely not running the same addon. I'm running the one posted in this thread.
When i went to test it out, i didn't have the variable for enabling, or setting the path to where, so i went and got them from this list, according to which the supposed values are indeed true / false, not 1/0.
Anyway, what ever you had to do to get it working, gratz.
B!

I think I had the least amount of success with SCP regarding the watch-dir. Maybe the file perms got screwed up because I'm copying over as root. Dropping the file into the dir with AFP/CIFS seems to retain the correct perms for it to work.

I definitely am using this version of Transmission (I have NV+ v1). Previously I was using Super Poussin's addon up to v 2.42 (where he stopped supporting it). Moved onto v2.8x when I found that it was available and continued to use Poussin's email script and settings.json file for config.

I've had no problems with watch-dir. And I am also using settings from old super-poussin's version, but I edited them and inspected each line carefully when switching to tarobun's version.

viewtopic.php?t=75559

Hi
I've problem with Transmission 2.84. I tried many search.
Any torrent would like start (private and public torrent), and i tried the SAME torrent file on a 2.84 transmission on my Laptop ubuntu and it works perfectly.
The configuration are same.

Transmission say :
Announce error: Could not connect to tracker - Today 06:23:20 PM
Next announce in 9 minutes
Scrape error: Could not connect to tracker - Today 06:25:05 PM


Config on Transmission 2.84 on ReadyNas Duo RAIDiator 4.1.14 :

{
    "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://www.example.com/blocklist", 
    "cache-size-mb": 2, 
    "dht-enabled": false, 
    "download-dir": "/c/media/BitTorrent", 
    "download-queue-enabled": true, 
    "download-queue-size": 5, 
    "encryption": 0, 
    "idle-seeding-limit": 30, 
    "idle-seeding-limit-enabled": false, 
    "incomplete-dir": "/c/media/BitTorrent/_incomplete", 
    "incomplete-dir-enabled": true, 
    "lpd-enabled": true, 
    "message-level": 2, 
    "peer-congestion-algorithm": "", 
    "peer-id-ttl-hours": 6, 
    "peer-limit-global": 200, 
    "peer-limit-per-torrent": 50, 
    "peer-port": 51413, 
    "peer-port-random-high": 65535, 
    "peer-port-random-low": 49152, 
    "peer-port-random-on-start": false, 
    "peer-socket-tos": "default", 
    "pex-enabled": true, 
    "port-forwarding-enabled": true, 
    "preallocation": 1, 
    "prefetch-enabled": 0, 
    "queue-stalled-enabled": true, 
    "queue-stalled-minutes": 30, 
    "ratio-limit": 2, 
    "ratio-limit-enabled": false, 
    "rename-partial-files": true, 
    "rpc-authentication-required": false, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password": "{c16e9303ec8d8827bad4d9e94a864103a087edc5bLqTQnoT", 
    "rpc-port": 9091, 
    "rpc-url": "/transmission/", 
    "rpc-username": "", 
    "rpc-whitelist": "127.0.0.1,10.0.0.*,192.168.*.*", 
    "rpc-whitelist-enabled": true, 
    "scrape-paused-torrents-enabled": true, 
    "script-torrent-done-enabled": false, 
    "script-torrent-done-filename": "", 
    "seed-queue-enabled": false, 
    "seed-queue-size": 10, 
    "speed-limit-down": 100, 
    "speed-limit-down-enabled": false, 
    "speed-limit-up": 100, 
    "speed-limit-up-enabled": false, 
    "start-added-torrents": true, 
    "trash-original-torrent-files": false, 
    "umask": 18, 
    "upload-slots-per-torrent": 14, 
    "utp-enabled": false, 
    "watch-dir": "/c/media/BitTorrent/_watch", 
    "watch-dir-enabled": false
}

And my 51413 port is open on my router, but transmission show "port is closed".
Upnp is turn on on the router.

And is the past, the add on works perfectly (10 days ago). I don't change any thing. I don't unterstand.
Is there a LOG file for Transmission 2.84 on the Nas Readynas Duo ? How and where I can find it ?

Is it possible that the internal IP address of the NAS has changed? (e.g., the port may be forwarded to the wrong IP address?)

Same thing is happening to me. Suddenly Transmission is not connecting to anything with message "Port is closed" but all signs indicated that the route is open. How to debug this?

Same question for you - did you verify that the port is still forwarded to the current internal IP address of the NAS?

Also you can verify the port status with http://www.canyouseeme.org/ from a PC.