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

Many thanks for this update.

Has the email alert function been removed?

I've configured my NV+ to use an external email server, installed the 'email_alert' script and changed the relevant setting to 'true' in the settings file - but it still doesn't work for me.

Am I missing something here?

Thanks
kels

btw heres the error that im getting whenever im trying to delete or move the file

you require permission to unix user\nobody to make changes on this file

i'm unable to transfer or delete files coming from the Bitorrent folder... it says access denied.. i can copy files without issue..
any help will be greatly appreciated

tarobun wrote:
*shrug* Works for me.

Me too mate.

Very grateful most are as well.

I find that if I don't use the '-f' (foreground) option the settings don't get saved when the addon is stopped. Probably should remove the --background option in start.sh as it is redundant in this case.

Not sure why you think TRANSMISSION_HOME is set incorrectly. It is set to '/c/addons-config/Transmission' which is where the settings.json is found.

For the binaries, I prefer to put all the files in one directory so they are easy for me to find. For me (and others I'm guessing) it doesn't really matter as we don't remote into the NAS to run the transmission commands directly. But feel free to move them to /usr/local/bin

*shrug* Works for me.

Here's my feedback on the addon.

In short words: No can do..

For instance:

in start.sh: transmission-daemon is send to the foreground by the '-f ' option. But when the start-stop-daemon is called to throw the transmission-daemon to the background, the command breaks on the first fact. The correct option would be the '-g' and than the location of the 'settings.json'file. But if you set the TRANSMISSION_HOME variable correctly, you don't need that option.
Second. The environment variable "TRANSMISSION_HOME" is set incorrectly. This must be set tot the same directory as where the 'settings.json' file is.
Third: binaries does not belong into the '/etc' directory. Binaries belong (in this case) in /usr/local/bin

By default the web ui is available at port 9091 of your NAS (ie. http://a.b.c.d:9091/transmission/web/)

If it's not coming up, try reloading/refreshing the web page or try with another browser.

If it still doesn't work try rebooting the NAS.

My old ReadyNAS DUO SPARC has decided to update itself to 4.1.3 and Transmission stopped working. I restarted, removed Transmission, reinstalled 2.82, started the service.
The daemons seem to be running fine, the service appears in the addons menu and I can start and stop it.
However the link to the UI just goes to a "blank" page. Looks like the WebUI isn't available via Apache.
Any ideas?
Thanks

Sorry for the noob question but I am having some issues. I got Transmission 2.82 installed and it looks like it is running but when I use Transmission Remote GUI to start a download, I get an error about tracker connection failed. I don't know if there are some settings I need to make on router or what because torch works fine on laptop. Currently running dd-wrt ver 24 sp 2. Let me know how to post screenshots or any other information you might need

dudeishere wrote:
1) I can't seem to get readynas to go through my router. I've open the port on the router (dir-655) I can confirm it is open when i point it to my laptop. I can confirm that the port is open on the readynas (netstat -a | grep 61688) but it always shows as closed on transmission. I don't see any mention on the log (using --logfile) this is what it looks like at startup:

Look in settings.json for ""port-forwarding-enabled":" and make sure it says "true" as argument. Then log on to your D-link router and make sure uPnP is enabled, it's under advanced network settings. If your running a old enough Firmware, your not going to have that setting, and will need to update first, then it will be supported. After that, you should be able to ignore it, more or less. It should always just work.

Now that i sort of fixed your issue, or, well, hopefully at least, here comes the kicker.
If, for what ever reason, the router / firewall whatever thats in between the ReadyNAS with Transmission, and the rest of the world is restarted, Transmission doesn't seam to notice that the uPnP port forwarding no longer works, and you go deaf. From what i see, it looks like new torrents will set up new forwarding, but the old stuff remains broken. Restarting the NAS will fix the issue. I assume this is something it inherits from the Transmission code it self, and that it has nothing to do with the ReadyNAS adaptation. But i thought i should put it out there. Might simply be my Firewall that is overly anal as well. (Smoothwall SWE3.0)
B!