New Transmission add-on thread

Hi, I have recently installed Transmission 2.11 on my ReadyNas Duo running Radiator 4.17.

I am able to upload and download OK. However, looking in Inspector on the web interface, I get "No Selection" displayed at the top of every section. No data is displayed in the "Information" or "activity" sections, whilst the "peers", "tracker" and "files" sections seem otherwise OK. Is anyone able to tell me what is going on / how to sort this out?

Just installed Transmission 2.11 but I haven't been able to add a torrent successfully.

I added a torrent to the sources folder and when I loaded up the interface the torrent had been added. A few MiB downloads but then it says:

Error: Permission denied (/media/BitTorrent/FILENAME) (see screenshot below)

Each torrent I add just gives the same message. Any help will be greatly appreciated!!

To potentially follow on from what seanmt was saying, I am seeing a similar problem. I have used Transmission for quite a while on different versions, and thought I'd fixed this, but now it's back.

Firstly, let me explain my setup. I have installed Transmission 2.11, which I wish to run as the "data" user, as that is the owner of my BitTorrent share (I am using the "Share" security mode). So I have a folder "/data/BitTorrent" which is owned by the "data" user and "nogroup" group which holds all my Tranmission downloads.

To ensure that files created and updated by Transmission are all created with the correct owner and permissions, I have modified the following file in the distribution:

/etc/frontview/addons/bin/TRANSMISSION/start.sh

Port=`cat /c/addons-config/Transmission/transmission-daemon/settings.json | grep "rpc-port" | awk -F " " '{ print $2 }' |  awk -F "," '{ print $1 }'`
sed -i "s/TRANSMISSION_PORT=*.*/TRANSMISSION_PORT=$Port/" /etc/default/services

start-stop-daemon --chuid data:nogroup --start --umask 0 --pidfile /var/run/transmission-daemon.pid --make-pidfile \
            --exec /usr/local/bin/transmission-daemon --background --nicelevel 8 --  -g /c/addons-config/Transmission/transmission-daemon

pidof transmission-daemon  | awk '{print $1}' >/var/run/transmission-daemon.pid

sleep 40
/c/addons-config/Transmission/transtart.sh

Then, before starting Transmission, I run the following commands to ensure the existing config and setup data is owned by data / nogroup

chown -R data /addons-config/Transmission/*
chgrp -R nogroup /addons-config/Transmission/* 

This seems to run fine, but then after a few days (without a NAS reboot or even stopping and starting Transmission) I get the errors seen above. I then use PuTTY to log into the ReadyNAS box, and surely enough, everytime it seems that the /addons-config/Transmission/transmission-daemon directory, and the files within it, are once again owned by nobody / nogroup as they used to be. All the other files in /addons-config/Transmission are owned by data / nogroup still, it's just this directory.

The error, therefore, comes from the /addons-config/Transmission/transmission-daemon/resume file not being writable as the data user. I suspect there is some maintenance thread / process which is somehow modifying / recreating these files as the default user (nobody), but I cannot figure out what is doing it ?

Fixing it is simply a task of stopping the server (via frontview), running the two lines above, and restarting the server (again, using frontview). Not a tough workaround, but sometimes the server can be down for a long period, and I'm unaware it's stopped working until I log into the web application and see the Permission denied errors like seanmt has posted above.

Anyone know what might be causing this change of directory ownership ?

EDIT - just happened again. Only thing that had happened was a backup job ran (not against any Transmission files). Grrrr... I also notice that another user has posted the same approach as a working solution for running Transmission as another user : viewtopic.php?f=36&t=49127&sid=ab100c48b78c8082135f1a46d84d0109#p283015 - but like I say, for me something keeps modifying the transmission-daemon directory ownership recursively whilst Transmission is running.

Thanks,
Ben

Hey guys!

I recently get a ReadyNAS Duo and just installed transmission-daemon 2.11. Everything works fine except that I'm getting slow download speed (max 2 mb/s). Same thing with all torrents even if many people are seeding.

I have a PC running Ubuntu Server, also running transmission-daemon with maximum download speed 12 mb/s.

Why are my downloads so slow on my NAS? Do I need to change something in settings.json?

Thanks
Henrik

I hade been reading every page and i can't see to find my answer,

How can you remotely control this client over the Internet, on my linux box i just put my dns address with the port of the web client and it ask me for the login and pass of the transmission of my pc, i can't seam to do the same with the tansmission web client of my Duo! any help or link to the answer will be very appreciated! thanks in advance!

Edit: Never mind i forgot to forward the ports on my dsl modem :shock: !! Thanks anyways!!

Bizarrely I'm now getting the permissions problems listed above (permission denied etc.) - I've never had this issue before. I had to ssh onto the NAS and change them to get the torrent to open.
The files are being created by 'nobody' in 'nogroup' now which I don't recall before, although had no specific reason to check. Is there a way to change the default create UID and GID of the torrent files?

Does anyone find a way to rename/move or seed a torrent from the readynas from any (specified) path? I often will download torrents directly into my media/videos folder and want to keep seeding from there so I can watch them while seeding.

I've been confronted to the same permission issue as described by seanmt and phantomwhale.
I've configured Transmission to download in a different share than the default one (/c/p2p/BitTorrent/ rather than /c/Media/BitTorrent), but I kept the default user to nobody:nogroup (so far...).

I couldn't understand how I could have permissions issues as I didn't change the default user and all my directories where following these permissions. Then, I had a look into /addons-config/Transmission/transmission-daemon/settings.json and I noticed that 2 path were hardcoded to the default download directory:
"incomplete-dir": "/c/Media/BitTorrent/Incomplete"
"watch-dir": "/c/Media/BitTorrent/sources/"

I think the "incomplete-dir" one is the root of the problem as (I guess...) Transmission probably download all the different chunks here until the torrent has completed. So, if the directory is missing or doesn't have the right permissions, Transmission throws a "Permission denied".
So, I've created the "Incomplete" and "sources" directories in my new share (and set the right permissions to nobody:nogroup) and changed the settings.json to point "incomplete-dir" and "watch-dir" to the new locations, and so far, so good, I can download without seeing the "permission denied" error again.

One last word, make sure you stop Transmission before making the changes in settings.json, and just to be sure, remove all your current torrents from the list and re-add them once you've made all the changes and restarted Transmission.

Hope this might help a few of you.

How do you change the user that files are downloaded as? Or do I need to create a new share for downloads instead of the default? I don't want to ope up the permissions on the media directory and even having the BitTorrent folder as 777 isn't enough.

I resolved the "permission denied" issue by simply disable the incomplete folder. In settings.json I changed to:
"incomplete-dir": "/c/media/BitTorrent",
and
"incomplete-dir-enabled": false,

works fine