New Transmission add-on thread

Transmission crashing on a Duo is in most cases due to settings that are to hard for the Duo. Changing the settings to ones that require less or the hardware (mainly memory) solves this.

I've got no idea where the problem comes from that Transmission does not start when the NAS boots up. I had it a while back on my Ultra 2, but I just tried to remember when it last happened and that was before the last update (of Transmission) I did, so it might be solved in the latest version. (or by something that was done by the update)

Hei Jarno,

Is this a setting that is easily changed? I do not think I saw any thread on this.

Hey Jarno

So your saying if I've got the latest version of transmission that this should not happen. Transmission should automatically start when I boot up my ultra?

Edit-
So I have been playing around and have more info on my problem, hopefully someone can help me. I'm pretty sure I have created that exact problem trying to get my log in working.

So, once I got transmission up and working, I noticed that it never prompt me for a log in or password. I could connect via ipad, laptop with remote gui and never asked for me to log in. I thought that this was important so I went looking in settings.json file (have no idea what I was doing) and changed "rpc-authentication-required": false, to "rpc-authentication-required": true. When I tried to restart the add-on I got a "failed to start" message but the light went green. Transmission was still cleary working and boom, it asked me to log in and worked great. I also could not get the web interface to work on my ipad. Once I rebooted the nas, transmission needed to be restarted.

I changed back settings to false and back to 100% operational including ipad but no log in. Any advice on getting my log in sorted? Maybe this could help the guys with the duo's.

Gav

@ Prostheta: you can change the settings of Transmission in a file called settings.json. It is located in the folder Transmission/transmission-daemon on a share called "addons-config".
You can find settings that proved to work for a Duo here. He has set rpc authentication on, so I guess it's working there too. You only have to change the password (change the part between "", including the {, to whatever password you want) and start Transmission again.

@ G man: I'm not saying it should not happen with the latest version of Transmission, just that I did not had any problems anymore after the update. That was also somewhere around my update to Radiator 4.2.20, so that might have got something to do with it as well. I've got "rpc-authentication-required" set to true and it's working fine for me.

I found the problem and it was a mistake with my settings. I had only changed the password in two of the .sh files. I changed the password in blocklist.sh and it's all good, I can log on and transmission starts up automatically when I boot my nas up. Transmission will not start unless passwords match in all 3 .sh files and the settings.json file.

I still can't log in to the web interface with iPad when rpc-authentication-required is set to true. One last problem to sort out.

Hi,

i hope someone can help me here.

I just updated to transmission 2.52 on my readynas ultra.
Before I uninstalled the older version and deleted transmission folder in addons-config.

But now, i've got the problem, that I cant start transmission via readynas webinterface.
I configured settings.json as it was, at least I thought i did :roll:


Via ssh it's possible to execute the start script (/etc/frontview/addons/bin/TRANSMISSION/start.sh).

So, probably there's only a problem with the permissions. May someone help me to correct them?
Which user starts transmission, when its started via readynas web-interface?


Thanks alot!

I had problems with permission's and I could still use the web interface. It was only when transmission wanted to write the file to the media folder that I got a permission error. It is something that you need to do anyway and this is the information I followed tho configure permissions. The information about user's and group's are in that post.
http://www.readynas.com/forum/viewtopic.php?f=60&t=58521&p=337088#p337088

Does the service start in front view and the little green light come on?

I've got no idea where the problem comes from that Transmission does not start when the NAS boots up. I had it a while back on my Ultra 2, but I just tried to remember when it last happened and that was before the last update (of Transmission) I did, so it might be solved in the latest version. (or by something that was done by the update)

There's no entry or startup script for transmission in the init.d folder on the NAS. I believe this is the folder the NAS/Linux processes for things to load on startup. Without an entry of some description in there, Transmission never will start on boot.

I think there is a bug in the start.sh script for this addon.

if [ $UPDGRADE_FW eq 1]; then
/sbin/ldconfig
fi

I am not entirely sure but its set to zero, perhaps it evaluates to nothing in the test. In any case, I was able to install transmission 2.52 and it did not spin forever, hooray. But when I tried to start it in front view, it spins indefinitely and does not start. I tried to use SSH to run the start script manually and the script gives an error at this test noted above.

The removal script does not appear to work either. I really should not ahve tried to install this after my previous attempts, but I really need transmission. it doesn't work and now I can't uninstall it either.

running the TRANSMISSION.remove script manually I was able to remove it fine. I don't know why it does not work from frontview, the addon appears to be broken for that too.

For the start.sh I fixed the bug and got it to work. by changing the UPGRADE_FW variable to a string using "NO" and "YES" instead of number 0 or 1. There was a typo in the name of the variable for the test at line 37 also. This made the script run and it did start Transmission finally, which seemed to work. However, frontview control did still not work. Trying to start it or stop it causes endless cursor spin, as does trying to remove it.