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

tarobun wrote:
I think they changed something in Transmission 2.8x... What is the umask value in your settings.json file? Can you try it with "umask":0 ?

I tried that and so far (two Torrents) it seems to be OK. Thanks.

flamesong wrote:

addam wrote: I'm having some issues with a specific tracker and the readynas. I have no problems when trying to download with transmission for mac. I get no seeders but no errors either. I alson notice that some downloads are slower to start now compared to before. How can I find out what's wrong? BR/addam I have experienced exactly the same problem going back over the last two years. Whenever it happens, I either find the same torrent on a different site or use a Mac BitTorrent client. I think I may have once reconnected to my ISP thus acquiring a new IP address and I think that also canceled the problem on that occasion but it didn't work consistently so I didn't continue with it. Anyway, I got the sense that my IP address may have been blacklisted by the tracker.

Okay, I'm happy(?) to hear that I'm not the only one with this issue.
But I have not had this problem before I upgraded to 2.82. Not sure if I can downgrade and se if it has any effect.
I really like the transmission add-on. Together with the remote-gui it is absolutely awesome.
If anyone has any ideas I can try I'm happy to listen...


Sent from my iPhone using Tapatalk - now Free

addam wrote:
I'm having some issues with a specific tracker and the readynas. I have no problems when trying to download with transmission for mac. I get no seeders but no errors either. I alson notice that some downloads are slower to start now compared to before. How can I find out what's wrong? BR/addam

I have experienced exactly the same problem going back over the last two years. Whenever it happens, I either find the same torrent on a different site or use a Mac BitTorrent client.

I think I may have once reconnected to my ISP thus acquiring a new IP address and I think that also canceled the problem on that occasion but it didn't work consistently so I didn't continue with it. Anyway, I got the sense that my IP address may have been blacklisted by the tracker.

I'm having some issues with a specific tracker and the readynas. I have no problems when trying to download with transmission for mac.
I get no seeders but no errors either. I alson notice that some downloads are slower to start now compared to before.
How can I find out what's wrong?
BR/addam

My Duo v.1 (sparc) runs Raidiator 4.1.12 and Transmission 2.82 (fresh installation, previously deleted S-P's 2.04 version that stopped work under 4.1.12).
Works just fine but there's one problem: I couldn't stop Transmission via Duo's web-interface in order to edit settings.json file.
Short after I've unchecked it's mark and pressed Save button (green light turns off) Transmission starts itself again, it's check-box is unchecked but green light stays on.
Somehow after some manipulation I've managed to change several parameters in settings.json but now I just can't set up Transmission Remote access 'cause there's no possibility to set rpc-whitelist parameter without stopping the daemon.
Maybe there's a way to manually stop Transmission?

Update: problem solved using different browser

tarobun wrote:
I think they changed something in Transmission 2.8x... What is the umask value in your settings.json file? Can you try it with "umask":0 ?

I wasn't sure if that was a reply to my post or not.

Anyway, I have just been trying to open the settings.json file and found that I could not open it or copy it the way I had been able to do in the past and even when I logged in as Admin (as opposed to my user account with Admin status), I could not open it without adjusting permissions - so I feel that something is quite wrong.

The umask value was 10 but I have changed it to 0 as you suggest and I'll wait and see what happens.

I think they changed something in Transmission 2.8x...

What is the umask value in your settings.json file? Can you try it with "umask":0 ?

I have been having a problem which, if I think about it, has only occurred since I upgraded to Transmission v2.8.1 and that is that I am unable to move anything out of the BitTorrent folder or rename anything in it or in subfolders. I am asked for my password which is then apparently rejected as the action is not carried out. If I copy the files to my MacBook, I have the same problem there with the only exception that my password is accepted.

The only way to do anything is to go into Frontview and reset the share's permissions but that needs doing every time because the next time I want to rename or move anything, it happens again.

I have been trying to figure this out for some time now but just realised that, as far as I know, it is only the BitTorrent folder that is affected. I don't see any mention of this issue in the release notes of 2.8.2 so I don't know if this is a known issue or just something which I am experiencing but I am wondering if Transmission is setting the file/folder permissions or maybe it is not doing something it should do.

Can anybody shed some light on this for me as it is driving me insane having to continuously reset permissions.

AlTaiR wrote:
When I alter the settings from the web interface; They apply but don't seem to alter the /addons-config/Transmission/settings.json file. Where do these get stored?

The settings.json file is only saved when the Transmission service stops (via the ReadyNAS FrontView addon services tab) or when the ReadyNAS shuts down.

spacecrap wrote:
I cannot find any file that is called start.sh.... :( maybe a clean install would do the trick?

The file should be in /etc/frontview/addons/bin/TRANSMISSION if it's not that the new version has not installed correctly. What version does it say on the ReadyNAS FrontView addon services tab?

spacecrap wrote:
And I'm starting to feel like a noob, but how do I enter a command line? I tried to find out on the www and ended up with putty icw. rootssh but it seems that the command line you noted has no effect.... (i know I'm missing something... but what)

If the command was run successfully you should be able to open/edit any files in /addons-config/Transmission -> No more "access denied".