Transmission add-on thread before MAY 2K10

[Grouty]

Thanks for the advice. Changing that fixed the problem. I can't remember changing the JSON file but I guess I must have. I think the only reason I might have dome this is to try to take advantage of the "Transmission can monitor a directory" feature.

CLI
•Some torrent files created with transmission-cli were invalid
all ticket closed

Web interface on port 8181[/b]
default user is : admin
default password is : password1
Bittorrent port is : 51413
Default Download path /c/media/BitTorrent/
PeerBlocklist updated each day
Settings can be changed in Frontview UI and in Transmission WebInterface and in /addons-config/Transmission/transmission-daemon/settings.json
scheduler for bandwidth is removed and now handled by settings.json
Transmission can monitor a directory

I would be very interested if I could get this to work but I can't see where to make the change. Does anyone know how this works?

Before I head off to wait for someone to point me in the right direction I just want to say how much I appreciate both the effort super-poussin puts into this project and the help and advice other forum users provide. It is truly a marvelous community.

[danlane]

I see that the watchdog script used to automatically remove the torrent from Transmission and unrar the files. Now that the script is no longer included with Transmission what is the generally accepted method of automatically unrar'ing completed torrents?

[super-poussin]

to watch for .torrent in /media/BitTorrent/sources/ modify settings.json like this :

"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 0

to

"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 1

auto unrar is no more supported

[danlane]

auto unrar is no more supported

Ok, is there a version of the old script around anywhere that I could take a look at, I'm sure I can get something up and running by myself even if it isn't supported. I've seen the one at mybookworld but presumably you have one which works (albeit with issues) on the readynas?

[Grouty]

to watch for .torrent in /media/BitTorrent/sources/ modify settings.json like this :

"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 0

to

"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 1

auto unrar is no more supported

So, for the sake of clarity, do I just add those lines to my .json file? I note that they are not present in my current one:

Code: Select all

{
    "alt-speed-down": 50,
    "alt-speed-enabled": false,
    "alt-speed-time-begin": 540,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": false,
    "alt-speed-time-end": 1020,
    "alt-speed-up": 50,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": false,
    "dht-enabled": true,
    "download-dir": "\/media\/BitTorrent\/",
    "encryption": 2,
    "lazy-bitfield-enabled": true,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": false,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": false,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": 2.0000,
    "ratio-limit-enabled": false,
    "rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-password": "{f8f10320ee358cfa5102e2468d3a94fae66fccbdrgG0DNz2",
    "rpc-port": 9091,
    "rpc-username": "",
    "rpc-whitelist": "127.0.0.1",
    "rpc-whitelist-enabled": false,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 5,
    "speed-limit-up-enabled": true,
    "umask": 18,
    "upload-slots-per-torrent": 14
}



[Grouty]

OK. SO I tried adding

"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 1

to the end of my .json file. In order to do this I

disabled the Transmission Add-on

opened the .json file

saved it

closed it

restarted the Transmission Add-on

However, when I look at the .json file again I find that all my changes have gone and it reverts to the one I posted earlier. When I say all my changes have gone I mean ALL of them. So I had disabled the rpc-whitelist, changed the download directory to the default

not

"download-dir": "\/var\/local\/\/Downloads",

but

"download-dir": "\/media\/BitTorrent\/",

and worst of all my

"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 1

had disappeared completely!

Very puzzling. I made all my changes a second time. Copied the file so I had a backup. Saved the .json file and restarted Transmission Add-on. Again, all my changes vanished when I looked at the .json file. Do I need to remove and reinstall Transmission? Any help gratefully received.

[btaroli]

You must stop (and be sure it's down) *before* editing the file. It updates it upon shutdown... hence the loss of your changes.

[Grouty]

You must stop (and be sure it's down) *before* editing the file. It updates it upon shutdown... hence the loss of your changes.

Thanks for the quick reply. I'm pretty sure I'm doing what you are telling me to do. In FrontView I uncheck the box beside "Transmission. P2P Client" and hit save. I get a pop up box telling be that the Transmission client has been stopped. I then open and edit the .json file, save it and close it before checking the box beside "Transmission. P2P Client" and hit save. I then get another dialogue box telling me the Transmission service has been started. Am I really doing something wrong?

I'm also confused at the behaviour of the .json file at close down. Why does the Add-on wipe out my changes to the file when I stop the service? Seems a little weird to me - but then what do I know?

[Grouty]

I thank you for all your patience because I am getting frustrated with all this. My settings are as follows (changes from default towards the end and bold):

{
"alt-speed-down": 50,
"alt-speed-enabled": false,
"alt-speed-time-begin": 540,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 50,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "\/media\/BitTorrent\/",
"encryption": 1,
"lazy-bitfield-enabled": true,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 51413,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.0000,
"ratio-limit-enabled": false,
"rpc-authentication-required": false,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{3d741d36e148c1c63fd293e277829baa53bb11fc.nluH7er",
"rpc-port": 9091,
"rpc-username": "",
"rpc-whitelist": "127.0.0.1"
"rpc-whitelist-enabled": false,
"speed-limit-down": 100,
"speed-limit-down-enabled": false,
"speed-limit-up": 100,
"speed-limit-up-enabled": false,
"umask": 18,
"upload-slots-per-torrent": 14
"watch-dir": "\/c\/media\/BitTorrent\/sources\/",
"watch-dir-enabled": 1

}

And I get a "403" error message when I try to open the Transmission interface. As far as I can see the rpc-whitelist entry is disabled so I assume I should be able to access the Transmission interface from the button on the FrontView page. Does anyone have any idea what I have stuffed up this time?

[tubalmartin]

Hi, I've been trying to get Transmission 1.73 to work on my Duo but it's been impossible.

My issue:
When a torrent is added, Transmission starts downloading it, but after 3 seconds, the torrent download stops and Transmission shows the following error message: "no such file or directory".

My config:
- ReadyNAS Duo (Raidiator 4.1.6)
- CIFS enabled and working
- Default access over CIFS on "media" share is set to read/write, and permissions on new files and folders are set automatically to read/write for groups and everyone (ACL checked too).
- BitTorrent add-on disabled
- I have every setting in Transmission by default, no modifications in paths or whatever.
- In Frontview I can't see the "addons-scripts" share, I can only see the "addons-config" share. Is that ok?

* Scripts are now in /addons-scripts/Transmission
* Config is now in /addons-config/Transmission
# To see this new share no need to reboot

- BitTorrent folder does exist on "media" share.



Please help, BitTorrent official add-on is not reliable (hangs/freezes randomly), Transmission is my only hope!!!

[super-poussin]

normally the BitTorrent directory is created by the nas , sounds like you remove it

so

you can try this version :

for sparc

for x86

[tubalmartin]

Thanks super-poussin for your quick response. I'll try right now that beta and let you know it this issue remains.

If you have any question, please make it, I need Transmission working on my NAS.

normally the BitTorrent directory is created by the nas , sounds like you remove it

The fact is I haven't ever removed the BitTorrent folder or modified its permissions. The official BitTorrent add-on have always worked on my Duo but due to its poor stability I'm forced to search for an alternative and Transmission is the perfect choice. (BTW Transmission is the client I use in my MAC)

[tubalmartin]

I have already tried 1.74b02 and unfortunately I get the same message when I try to download a torrent: "no such file or directory"
In Frontview I don't see the "addons-scripts" share yet, is that ok?

What user does Transmission use? I wonder if it's a matter of permissions...

Thanks in advance

[super-poussin]

can you rebot your nas ans also check what you have in /media ?

can you also post your settinfs.json file content ?

[tubalmartin]

Thanks super-poussin but I've already SOLVED IT!!!!!

It had to do with permissions...days ago I changed the owner of the "media" share from "nobody" to my user name "tubalmartin" ("media" Share -> CIFS -> Advanced options). I have switched to "nobody" again and give the owner read/write permissions and everything works perfect...torrents are downloading fine now.

Now let's enjoy Transmission!!!!!!