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

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

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.

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!

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:
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!

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.

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.

Thanks!...

Updated to version 2.84

Changes:
All Platforms

• Fix peer communication vulnerability (no known exploits) reported by Ben Hawkes

Transmission 2.83 is vulnerable to peer communication vulnerability. More details are available in Gentoo bug tracker at https://bugs.gentoo.org/show_bug.cgi?id=516822. Version 2.84 contains fix for this vulnerability.

Thanks for the new version tarobun!
Just updated, wokring fine.