Transmission 1.42+ for DNS-323 (148)
Updates
30th January 2010 – Updated guide with solution to fix problem when upgrading from 1.76 to 1.82/1.83
30th January 2010 – Updated guide to install transmission 1.83
27th January 2010 – Updated guide to install transmission 1.82
24th January 2010 – Updated guide to install transmission 1.80
25th November 2009 – Updated guide to install transmission 1.76
26th August 2009 – Updated guide to install transmission 1.74
20th July 2009 – Updated guide to install transmission 1.73
23rd June 2009 – Updated guide to install transmission 1.72
9th June 2009 – Updated guide to install transmission 1.71
7th June 2009 – Updated guide to install transmission 1.70
14th May 2009 – Updated guide to install transmission 1.61
2nd May 2009 – Updated guide to install transmission 1.52
28th Feb 2009 – Updated guide to install transmission 1.51
24th Feb 2009 – Updated the guide to install transmission 1.50
Decided to write this post as there are still users refering to the set up instructions for transmissionbt prior to 1.42. There has been some changes and therefore the previous guide’s instructions aren’t exactly correct now. By following the old guide, you would probably end up seeing the following:
401: Unauthorized
Unauthorized IP Address.Either disable the IP address whitelist or add your address to it.
If you’re editing settings.json, see the ‘rpc-whitelist’ and ‘rpc-whitelist-enabled’ entries.
If you’re still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.
Hence this guide aims to set up transmission from scratch. In this guide, I refer to the IP address of your NAS as A.B.C.D. Hence, in all occurrance of A.B.C.D, replace it with your NAS’s IP.
If you have followed the old set up guide “Transmission for DNS-313, DNS-323” just follow guide from the section on “Updating the whitelist” to complete the setup.
If you need to edit settings.json for the rpc-whitelist, you can check out the steps in the section “Updating the whitelist” in this guide.
Prerequisites
Ensure that you have fonz’s fun_plug 0.5 installed on your NAS. If you are using DNS-323 or DNS-343, follow the guide “Running fonz’s fun_plug (0.5) on DNS-323“. If you are running DNS-313, follow the guide “Running fonz’s fun_plug (0.5) on DNS-313” instead.
Once you have fonz’s fun_plug up and running. Carry on to the next section.
Installing uclibc
- Click on Start -> Run
- Type “cmd” without the quotes and hit <Enter>
A command prompt should appear - Type the command “telnet A.B.C.D” into the command prompt and hit <Enter>
You should be greeted by the command prompt “#”.
- Type the command “cd /mnt/HD_a2” and hit <Enter>
The prompt should change to “/mnt/HD_a2 #” - Type the command “wget http://www.inreto.de/dns323/fun-plug/0.5/packages/uclibc-0.9.29-7.tgz” and hit <Enter>
There should be a downloading process. Do not interrupt it and wait for the prompt to reappear - Type the command “funpkg -i uclibc-0.9.29-7.tgz” and hit <Enter>
- Finally reboot the NAS using the command “reboot”
The command prompt may end and close by itself
Wait for the NAS to be online before going to the next section.
Installing Transmission
- Click on Start -> Run
- Type “cmd” without the quotes and hit <Enter>
A command prompt should appear - Type the command “telnet A.B.C.D” into the command prompt and hit <Enter>
You should be greeted by the command prompt “#”.
- Type the command “cd /mnt/HD_a2” and hit <Enter>
The prompt should change to “/mnt/HD_a2 #” - Type the command “wget http://kylek.is-a-geek.org:31337/files/curl-7.18.1.tgz” and hit <Enter>
- Type the command “wget http://kylek.is-a-geek.org:31337/files/Transmission-1.83-1.tgz” and hit <Enter>
- Type the command “funpkg -i curl-7.18.1.tgz” and hit <Enter>
- Type the command “funpkg -i Transmission-1.83-1.tgz” and hit <Enter>
- Type the command “chmod a+x /ffp/start/transmission.sh;sh /ffp/start/transmission.sh start”
There would be a message like starting transmission - Type the command “sh /ffp/start/transmission.sh stop” and hit <Enter>
There would be a message like stopping transmission - Do not close the command prompt.
Updating the whitelist
In this section we would be adding your local lan IP range (A.B.C.*) to the whitelist. Assuming your NAS’s IP is 192.168.1.101, A.B.C.* would simply mean 192.168.1.* where the last group of number becomes asterix (*).
- Go back to the command prompt
- Type the command “vi /mnt/HD_a2/.transmission-daemon/settings.json” and hit <Enter>
- Shift the cursor using the arrow keys to the line with “rpc-whitelist”
- Hit the <End> key
The cursor would shift to the end of the line containing “rpc-whitelist” - Hit the left arrow key two times
The cursor would shift onto the ” at the end of 127.0.0.1 - Hit the i key
The “-” at the lower left hand corner of the command prompt would change to “I”. Hitting the <Esc> key would change it back to “-”. - Ensure that “I” is at the lower left hand corner of the command prompt
- Type the following “,A.B.C.*” (remember to replace it according to the instructions at the start of this section)
The entire line would read something like
“rpc-whitelist”: “127.0.0.1,192.168.1.*”,
- Hit the <Esc> key
- Hit the : key
The symbol at the lower left hand corner of the command prompt would change to “:” - Type the following “wq” and hit <Enter>
The file would be saved and you will be returned to the prompt
Starting Transmission
- Type the command “sh /ffp/start/transmission.sh start”
There would be a message like starting transmission
Give it sometime for transmission to startup before proceeding to the next section.
Setting the download directory
- Type the command “su nobody -c “mkdir -p /mnt/HD_a2/transmission-downloads”“
- Type the command “transmission-remote 127.0.0.1 -w /mnt/HD_a2/transmission-downloads”
There would be a message like success
It’s done! Direct your Internet browser to http://A.B.C.D:9091 for the transmission web user interface.
Facing issues with Transmission?
Having issues with Transmission 1.82/1.83 after upgrading from 1.76?
Some of you may face problems connecting to the Transmission web interface after upgrading to 1.82/1.83 from 1.76. What you can do is remove the settings.json file. By doing so, you will lose the configuration for Transmission but not your downloaded data. Follow the following instructions to remove the file
- Telnet to your NAS by following the instructions for steps 1-3 in the section Installing uclibc
- Type the command “sh /ffp/start/transmission stop”
There would be a message like stopping transmission if transmission is running - Type the command “mv /mnt/HD_a2/.transmission-daemon/settings.json /mnt/HD_a2/.transmission-daemon/settings.json.old”
You have renamed the settings.json file to settings.json.old - Follow the guide starting from section Installing Transmission until section Setting the download directory to install the latest transmissionbt
This would fix the common problems faced when users upgrade from 1.76 to 1.82/1.83.
Like to buy shadowandy a cup of Starbucks for his work?
Note: Transmission is now being actively compiled by KyleK. You can check out this thread.
Loading ...
For some reason, this post cant display on my Interenet Exploerr. works fine on Firefox.
Andy,
there seems to be a problem accessing your site via IE7, at least that is what I have tried.
Hi Shadowandy,
Have you tried using Transmission Remote GUI
http://code.google.com/p/transmisson-remote-gui/
This multiplatform app instead of the web interface?
Its much better, permits selecting files to download within a torrent, you can set priorities and set bandwidth on a per torrent basis.
Cheers!
james & wenwei,
Seems like one of the Wordpress plugin is giving the problem. Have disabled that plugin and it seems fine now.
Index Monkey,
Yeap! Been using it!
Excuse me, shadowandy – i’d like to know if I install / chroot to debian, can I run iptables on DNS-323? How can I have iptables on it?
Hi shadowandy,
there is new version of transmission released (1.50 beta 1)
would you build it for us?
Isildur,
I don’t compile them anymore. KyleK is compiling them. I’m just updating a dated guide.
Andy…Tried, and I’m getting:
wget: cannot connect to remote host : COnnection Refused
Robbo,
Do check your internet connection. I’ve no problem getting the files.
[...] guide has been superseded by “Transmission 1.42+ for DNS-323“ Required [...]
Using Transmission 1.42-1 on my DNS-313, with Transmission Remote GUI or Clutch and see my bitrate, is not stable
If I DL/UL the same file on Transmission, or Utorrent, Utorrent is much faster and have less variations in DL/UL transfert.
Don’t understand, my transmission port is forwardding in transmission and marked open in my Router
Does someone have an idea?
Thx a lot for your tutorial who help me a lot.
The directions helped a lot – got me farther than I was before.
Unfortunately, I can only connect to the Web interface for a few minutes before it seems like the Transmission daemon crashes, and the interface goes down.
Via telnet, I can’t see anything Transmission related when i ps -a, leading me to again think that the daemon is crashing.
Anyone have similar experiences or advice?
hey acnicklas…the initial release of transmission 1.42 had this weird issue in the code where it called some assert command. Basically Transmission kept shutting down everytime I used the WebGui. Not sure if it also happens on the command line. I ended up just using an older version of Transmission waiting until a stable release comes out and KyleK compiles a version for the DNS-323
Just wanted to give a big thanks to ShadowAndy for this Guide.
I am long time Windows user but completely new to Linux. Followed this guide to the letter (well cut and paste, it was pretty easy) and it worked like a charm!
Also a thanks to Index Monkey for suggesting using the Transmission Remote GUI, I got this working also and it is fantastic. (much better than the Web Interface)
Now I am working on figuring out permissions and such as I (on my pc with a mapped drive on the 323) don’t seem to have write permissions into the directories created by Transmission… so much to learn, ah the fun of it all!
Northern Paladin,
You are welcome.
Permission settings you can pretty much google it. Learn about the different user groups and write, read, execute bits.
Thanks for the link to the updated version and information about the install.
One thing that took a while for me to figure out – having already installed Transmission 1.34 – was that the “funpkg -i Transmission…” command wouldn’t work (reporting that it was already installed).
It seems obvious in retrospect, but – for others who might be confused – the trick was to just run “funpkg -u Transmission-1.42-1.tgz” instead, to force the upgrade.
shadowandy ,
Another excellent guide!! Thanks..
I am not trying Transmission. Nicer interface. Let’s see if it works
When I uploaded my first torrent, it showed up in the list, and then I got a popup saying “Could not connect to server, you may need the page to reconnect”
Then I think Transmission crashes! I have to start it again. If I look in the log file I see:
Flushed.Away.Trailer.720P: Couldn’t read resume file
Flushed.Away.Trailer.720P: Queued for verification
Flushed.Away.Trailer.720P: Verifying torrent
Flushed.Away.Trailer.720P: Got 17 peers from tracker
Couldn’t create “//Flushed.Away.Trailer.720P”: Permission denied
/ffp/bin/transmission-daemon: bandwidth.c: 428: tr_bandwidthUsed: Assertion `tr_isBandwidth( b )’ failed.
Flushed.Away.Trailer.720P is the torrent file name…
Did we miss to chmod any folder during the instructions?
When are you releasing a guide for the Transmission? Thanks
Thanks…
shadowandy,
Figured it out
Default location was “/”. I just put in a proper path, and chmod it to 777…. That worked.
My only comment is that transmission crashed a lot… Looking forward for the new version.
Thanks…
Guys,
Is anyone noticing that Transmission is great in downloading, but h ardly any downloading happening!?! I hardly see any download even though one of my torrents has 611 peerss??
I have set it up for 50kb/s upload!
Thanks.
finally i got a decent speed with transmission.. i give up on mldonkey and tried transmission.. u have no idea how many times i’ve re-installed mldonkey and ffp and finally it paid off with this guide. thank you.. =)
Shidi,
MLDonkey comes default with IPFilter to make P2P safer. It blocks out certain nasty IP ranges which the default installation of Transmission doesn’t provide.
Some people swear by IPFilter to block out anti-p2p companies. Hence the speed is a trade off.
And Transmission doesn’t do other p2p protocols such as edonkey.
alamak then transmission cannot add ipfilter?
mldonkey so much trouble after load miserable dwnld speed.. kaoz…
and the build in bt client in dns 323 also same like transmission w/o ip filter..
Shidi,
You can add in ipfilter. Search around. If I am not wrong, I have written the guide for blocklist downloading and adding blocklist support to Transmission.
ok tks..
got it now =)
1 erroro fixed
new error
log
Transmission 1.42 (7500) started
RPC Server: Adding address to whitelist: 127.0.0.1
RPC Server: Adding address to whitelist: 192.168.1*
RPC Server: Serving RPC and Web requests on port 9091
RPC Server: Whitelist enabled
Loaded 2 torrents
Timbuktu 8.6: Got 17 peers from tracker
MacOSXUpdCombo10.5.6.pkg.zip: Got 12 peers from tracker
Port Forwarding: Opened port 51413 to listen for incoming peer connections
Searching for web interface file “/home/nobody/.local/share/transmission/web/javascript/transmission.js”
Searching for web interface file “/ffp/share/transmission/web/javascript/transmission.js”
Invalid socket argument
Help !!!!!!!
Andy, seem i made some mistake…
i tried to tape the command: “vi /mnt/HD_a2/.transmission-daemon/settings.json”
and I have got the following:
whole screen of such simbols
~
~
~
- /mnt/HD_a2/.transmission-daemon/settings.json 1/1 100% – at the end of screen
Please, help me to find out what I made wrongly.
THX,
Andrey
Hi shadowandy thanks for the guide to setup transmission on dns-323
without this guide i think is totally impossible for me to set it up! all the command are so alien to me..
Btw can i check with you is it normal for transmission preferences setting to reset everytime i reboot/shutdown my dns-323?
Thank again
andre,
You are welcome
.
Transmission’s preferences should persist across reboots.
Hi.
I have just bought a DNS-323 and installed Fun_Plug on it. I have tried to install transmission but it do not seem to work. I can login to Transmission via both the WebGui and clutch… I can add torrents but just when they start the server disconnect and say “Connection failed”. What could be the problem. I have also tried Transmission remote gui and I can log in, add torrent but as soon as it is supposed to start downloading it says “Connection refused”. The thing is that I can see all the stats about the torrent, seeders, leachers etc.
I am very new to this so plz be gentle..
Thanks alot Shadowandy !!!
btw, i noticed the download directory was defauted at a different location,
I changed it to my original pre-1.42 transmission settings
“download-dir”: “\/mnt\/HD_a2\/ABC”
where ABC was my torrent directory on the dns323 volume. I got clutch to work right now, verifying the partial downloaded data now…
hi andy, great post. however it would be great if you could have a tutorial for setting up DDNS for dns-323 so users can access it at work. cant find any guide on that online and if there is, it isnt that comprehensive enough for ppl that arent tech savvy.
hi andy excellent post and very thorough! the url for the download is not reachable anymore, do you know if there is a mirror somewhere? (http://kylek.is-a-geek.org:31337/files/Transmission-1.51.tgz)
I’ve also tried getting the latest transmission via wget, but getting connection refused.
ling & Kim,
The website belongs to the guy who packaged transmission for DNS-323. Perhaps you can check this out.
Hi I am getting this erro rmsg.
root@DNS-323:/mnt/HD_a2# funpkg -i transmission_1.51.tgz
FATAL: transmission_1.51.tgz: /ffp not found in package
Can someone give me some advise?
Andy, this post is fantastic, thanks for putting it up and maintaining it. I am having the same issue Kim reported with Connection refused for the Curl and Transmission library files from Kyle’s site. I was able to get the Transmission file from the alternate site you provided 2 posts up, but can’t find an alternate site for the Curl files. The main curl web site has a lot of different versions for different platforms. Any chance you could provide an alternate link for that library that works with the DLink?
Thanks again
I’ve that problem, at after 5 sek dl. Transmission say’s “no such fil or diectory”
I have made a download directory “/Volumes/Volume_1/Download”, but It will not accept it under perferences in >Transmission Web Interface..
My NAS is a DNS-323 fw 1.6
Plz help, is confuse
Stryx,
Volume_1 is actually /mnt/HD_a2. So if I want the transmission to download to a folder “download” in Volume_1 (Volume_1/download), it is actually /mnt/HD_a2/download.
Hope it helps.
Thx for the help, men I get the same messages even with /mnt/HD_a2/download i preferences… I just can’t see what I’m doing wrong here
Linux isn’t my strong side
Thx for the help, but I get the same messages even with /mnt/HD_a2/download in preference. And the mappe do exist… I just can’t see what I’m doing wrong here
Linux isn’t my strong side
Hi
i have the same problem the web interface gave me and error after a few secs of downloading “no such file or directory”
and the preference setting is mnt/HD_a2/Downloads/
my setting file in /mnt/HD_a2/.transmission-daemon/settings.json
is showing
“download-dir”: “mnt\/HD_a2\/Downloads\/”
but if i use transmission-daemon -d command
it shows “download-dir”: “\/\/Downloads”,
please advice.
btw i have successfully installed MLdonkey and it worked,
i don’t think there is something wrong with the network settings
Hakushi,
it is /mnt/HD_a2/Downloads instead of mnt/HD_a2/Downloads
Hi,
I was tryig to setup clutch with transmission 1.51.
Things were fine till the point where i have to point the link to transmission socket.
echo “/mnt/HD_a2/.transmission/daemon/socket” > /mnt/HD_a2/www/pages/clutch/remote/data/socket.txt
In this version of transmission 1.51 (using Kylek’s compiled version), there is no socket file.
My transmission home directory is /mnt/HD_a2/.transmission-daemon.
There is also no “-s” option to create the socket from /ffp/start/transmission-daemon. For e.g. -> http://linux.die.net/man/1/transmission-daemon
The end result cause Clutch to prompt for transmission daemon when clutch is launched.
Can I know if you manage to get Clutch to work with Transmission 1.51 (using Kylek file)?
camelbak75,
The standard installation comes with Clutch. Why do you want to install it again?
Hey shadowandy,
Keep up the good work! I’m a newbie & your instructions were even clear enough for me to get Transmission running…Many thanks to u!
Hi!
I’ve installed transmission and it’s working fine until I’m going to download files bigger than 300Mb.
Does anyone have the same problem? Is there any solution?
Small files dowload very fast and I would love to do it whith bigger ones too.
Thanks! (and thanks for this small guide!
)
Shadowandy,
I have followed the instructions here and it works great. thanks. What I have installed was 1.51
Are there any instructions on how to upgrade it to 1.52?
thanks
To upgrade, just download the 1.52 file and re-run funpkg, basically:
# Type the command “wget http://kylek.is-a-geek.org:31337/files/Transmission-1.52.tgz” and hit
# Type the command “funpkg -i Transmission-1.52.tgz” and hit
But I noticed that transmission 1.60 is out, any one knows when/where we get that built for our nas?
Hi Shadowandy,
I have upgraded Transmission from 1.51 to 1.61. How do I know the upgrade when successfully? There is no version number on the WebUI to confirm.
Regards
badduck,
You have to check it using transmission-remote through shell.
Andy,
I could not get the same response when i “vi /mnt/HD_a2/.transmission-daemon/settings.json”.
I have got the following response back, seems like the file is empty
~
~
~
- /mnt/HD_a2/.transmission-daemon/settings.json 1/1 100% – at the end of screen
Any ideas?
Many thanks!
Alex
Ok Never mind I got it to work liao. Somehow in my setup the correct path for the setting.json file is on HD_a4 not HD_a2
“vi /mnt/HD_a4/.transmission-daemon/settings.json”
Alex,
Are you using DNS-313?
Hi Andy,
Yes I’m using DNS 313. Although i think i have finish setting up, I’m not able to download anything. I’m using Transmission 1.61 and the Transmission Remote GUI. I can see that after I click start that it sort of talk to and find out the no. of seed and download would begin but would stop almost immediately with error message “no such file of directory”
Alex,
Make you have have set up the directory which transmission can download to. And also make sure the directory can be written by user “nobody”
Andy,
You may be right, as I can ping outside world from the DNS. Can you tell me how do I check the directory permission and how do i change it assuming it was because of permission issues.
Thanks!
Alex
Alex,
Think we managed to solve your problem over email a few days back right?
Hi Andy,
I upgraded from 1.42 to 1.61 using the 1.61 from the link you gave.
What I did was
1. “funpkg -r Transmission-1.42-1.tgz”
2. “”funpkg -i Transmission-1.61-1.tgz”
uninstall and install was successful, and can see from transmission-remote that its now running 1.61.
However, once I add in any torrents to download, it will tell me “no such file or directory” on the Web UI.
I have “chmod 0755 -R /mnt/HD_a2/torrents” (where /mnt/HD_a2/torrents is the directory for my downloads.
I have also changed the download directory in settings.json to “\/torrents”
Interestingly, all old torrents which were not completed earlier (before the upgrade), are still downloading fine after verifying.
Anyone has any idea what the problem might be?
Oh, there is also sufficient HD space. I have at least 300GB left and the file I am downloading is less than 1GB.
just to add on.
my /mnt/HD_a2/torrents and /mnt/HD_a2/.transmission-daemon directory can all be written by nobody.
infact, even when I changed the permission of /mnt/HD_a2/torrents to permission 777, same thing happens – i.e. No such file or directory
and in settings.json, I have tried some variations like “\/torrents”, “\/torrents\/”, “\/torrents\”, “\/torrents/”.
And everytime before I change anything, I will stop transmission first, change the settings, reboot, then once up, check the settings again to make sure that its running the new settings, and then run the torrent from the Web UI.
Unfortunately, non is working.
Can’t wait for 1.7. It finally appears to support DHT!
Can I beg? please pretty please!
hangyong,
Try setting the download directory either through the clutch interface or use the “transmission-remote 127.0.0.1 -w /mnt/HD_a2/torrents” command.
Marko,
Check out the guide. It was been updated for 1.70
Thanks shadowandy! That was quick!
Marko,
Not me. I think KyleK heard your request.
Hey all, great tutorial and tips. I could use some help though. I am running 1.70.2, and after a certain period of time downloading a torrent, the webgui locks up and i am no longer able to watch whats going on. The LAN light on the dns323 continues to blink, so i would assume that the download continues. I am also able to ping and stop/restart the daemon. But without forcing a reboot, i am not able to get the webui back. I am a little new to this, can someone give me a hand? I ran a (what was it?) strace i think, and it stops…i would attach the strace log but i dont think i can here?
No biggie but the title of the article could be updated to reflect the version change – i.e. 1.7 and no longer 1.42.
Thanks heaps for this information, I’ve had a DNS-323 for a while and have emigrated so am waiting for the ship to arrive – it’s in the container!
I’ll be giving this a go when it arrives – fingers crossed
Darren
So I have my DNS-323 with 2 mirrored 1TB drives in it, running 1.05 firmware on the NAS.
I copy fun_plug to volume_1 and boot, no telnet.
Is the HD_a2 still correct if the drives are in RAID 1 / mirrored config?
I have tried editing the fun_plug.sh file to HD_a1 and still no go.
Any thoughts anyone? Keen to see Transmission going, the standard client on the DNS won’t even add a torrent file to download!
Darren
Darren,
The files are “fun_plug” and “fun_plug.tgz”. Most of the problem arises when user save them wrongly as “fun_plug.sh” and “fun_plug.html”
thanks for the guide shadowandy! everything is fine until the part where one has to edit the settings.json.
appears that is is full of
~
~
~
~
have i done anything wrong? Thanks in advance.
ty,
Make sure you have started Transmission at least once (as mentioned in the guide). It should create settings.json automatically.
hmmm just did ‘ls’..my settings.json is not in /mnt/HD_a2/.transmission-daemon!! where could it be?!! sorry i just started messing arnd with my dns-343 so pardon me for my ignorance..
ok shadowandy! i got it! thanks..i did not start it at first.
hi shadowandy..sry to bother again =X i followed your instructions and checked again and again whether my nas’s ip is added to the whitelist
“rpc-whitelist”: “127.0.0.1,192.168.0.100”,
with 192.168.0.100 being my nas’s ip. still when i keyed http://192.168.0.100:9091/ into my web browser, i still get
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you’re editing settings.json, see the ‘rpc-whitelist’ and ‘rpc-whitelist-enabled’ entries.
If you’re still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.
Any thing that i missed out?
I did kill transmission before i altered whitelist.
hi shadowandy,
I have also changed “rpc-whitelist-enabled”: true, to “rpc-whitelist-enabled”: false,
didnt seem to work either…hmm…appreciate it if u can drag me outta this mess =)
thanks in advance!
ty,
according to the guide, the whitelisted ip you should enter is 192.168.0.* instead of your nas ip of 192.168.0.100
hi shadowandy..thank you so much! it works beautifully now!
Hi Shadow,
I tried your suggestion, but it did not help.
However, interestingly, after upgrading to 1.72, all is well… funny
Thanks!
Hi shadowandy, thanks for the guide.
Hi Andy,
I juz installed Transmission 1.72, but I keep getting this error
parent folder “/home/nobody/Downloads” does not exist
Can guide me how to troubleshoot it?
Zed
hi Andy,
I think I got it figure out, Thx for the great guide given!
Zed
Hi Andy,
Right now my Transmission is running smoothly, but when I’m accessing the DNS-343, either by streaming or copying files, do you experience connection being cut-off after about 10sec? it seems like while Transmission is downloading, I cant access the DNS-343 much.
Zed
Zed, what exactly did you do? I have the same error, and realize that it’s because indeed, the directory does not exist.
But – what is the best way to sort it out? What sort of permissions does it need, for example? Is the correct directory:
/mnt/HD_a2/home/nobody/downloads? or
A.B.C.D/home/nobody/downloads?
I will try to sort it out, and update this post, but if you’re still around, Zed, please send along a clue.
Cheers,
e.
OK – it just took two minutes scanning higher in the comments here.
All I had to do was create a folder:
/mnt/HD_a2/downloads (e.g.) and point Clutch’s preferences to it.
This is my second install of clutch, the first worked for over a year, then I updated h/drives – and lost all the data on two drives.
I’m now trying to recover the data, and in the meantime, installing the Transmission again was so so easy this time. But I am unclear about the what is secure or otherwise. For example, I was able to create the folder from windows without authentication, so my dns 322 is apparently wide open (at least from within my lan, not sure about http, e.g.).
Anyway, thanks again to Andy (bought a coffee last time).
e.
v1.73 just got released
Great work, all of you who have offered help here!
I have a small problem. I have Transmission Web Interface working, and hauling torrents for me. The other day, however, I had to reboot the device and lost all contact with it. I managed to get it back up and running, and my existing torrents were working (after waiting some time to verify the files).
However, now any new torrents that I add get Paused, then if I resume them, they run for a moment then come back with “Permission denied”. They are pointing to the same folder as the existing torrents.
Any ideas?
Here’s my settings.json file:
{
“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,
“completed-dir”: “”,
“dht-enabled”: true,
“download-dir”: “\/mnt\/HD_a2\/Torrents”,
“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”: true,
“rpc-bind-address”: “0.0.0.0″,
“rpc-enabled”: true,
“rpc-password”: “(we’ll leave this part out!)”,
“rpc-port”: 9091,
“rpc-username”: “Jeff”,
“rpc-whitelist”: “127.0.0.1,192.168.*.*”,
“rpc-whitelist-enabled”: true,
“speed-limit-down”: 100,
“speed-limit-down-enabled”: false,
“speed-limit-up”: 100,
“speed-limit-up-enabled”: false,
“umask”: 18,
“upload-slots-per-torrent”: 10
}
If it helps… I have never been able to get the Transmission remote gui to work either. Again, permission errors (“Connection Refused”).
Thanks!
Well, I came downstairs this morning to find that I no longer have permission to any of my downloads. I chown’d the folders to my name, but I am still unable to resume any of my previous downloads.
I really doubt that I’ll ever buy a D-Link product again…
After several attempts, CHOWN finally resolved my permissions issue. So my two complaints above are resolved. Not sure why the permissions fell apart in the first place, though.
I think, given the multitude of other issues that I’m having with the DNS-323 that I’m going to spend the next couple of days copying out the data on it and reformat the drives. Hopefully this will let me get past some of the bigger problems that I’m having with this NAS box.
Keep up the good work on this site, it’s been helpful!
Cranky,
Some users run into permission problem. Don’t really know what has been done. Did you accidentally recursively set the permission for /* ?
Hi Andy,
Thanks for the guide!
Got Transmission up, but not running exactly… Being a Linux illiterate, I’m not sure what’s meant by /mnt/HD_a2/ ?
The 323 is mapped as drive X in WindowsXP so I guess I’m not seeing the same names as in Linux. I’ve used this to set the download folder – transmission-remote 127.0.0.1 -w /mnt/HD_a2/Downloads – and it reported success, but the web gui still says “no such file or directory”. I set the same location in the web gui preferences.
Where should I have that folder? At the moment it’s in the root of X. Is that right?
Ginch,
Make sure you have Downloads folder in your Volume_1.
Andy,
Thanks – that’s where it is, but I’m still getting “no such file or directory”.
Any ideas?
Ginch,
Make sure the folder is writable by transmission (nobody).
Can anyone tell me if the proxy works on transmission….. I swear it doesn’t. I’ve added these settings.
“proxy”: “canada.btguard.com”,
“proxy-auth-enabled”: true,
“proxy-auth-password”: “foo”,
“proxy-auth-username”: “bah”,
“proxy-enabled”: true,
“proxy-port”: 1025,
“proxy-type”: 2,
With the older version of transmission, it was open to connections from the internet by default. I don’t see any discussion of doing that – is it unsafe to allow connections from anywhere, to a given port (e.g. 9091 in this case)?
If it is ok to do this, should I just ‘disable’ the rpc-whitelist? Would that allow connections from anywhere? I would of then password protect access to the application as described above.
I ask because I’m going to a friends just now, and wanted to connect to transmission from there without getting his ip addy beforehand.
Rgds,
e.
epiphanius,
Just use a wildcard to whitelist all IP
i have problem downloading using the dns 313. the download will start for a initially and then it will stop at certain percentage, eg it download until 48% and then it does not seem to download anymore.
what could be the problem?
fishball,
Does it happen to every torrent or only a particular one?
it happens to every torrent. my friend had the same problem too. when i use the torrent on my PC it manage to download without any problem.
the torrents will also flutuate within a certain percentage. eg you see that it is 48.7% now and then a few hours later when you check again you see that it is 46% as a result the download almost never complete.
fishball,
How big are the torrents? Honestly, I’ve yet to encounter such problems myself so I could not advise on that. Probably can look at the transmission log to see if there are any errors.
andy,
i observe that the problematic torrents their downloading arrow are red in color. also they have problem connecting to tracker.
i am downloading three file each abt 1 gb. could it be that i am downloading too many at the same time and the nas couldn’t take it?
i tried downloading open office and it works fine. so i think the problem lies with the torrent…
fishball,
Glad that you managed to find that it is the problem of the torrent. Some unhealthy torrents will take a long time to complete.
“Just use a wildcard to whitelist all IP”
Thanks, Andy.
e.
Hi fishball and Andy,
I’m having the same problem with my DNS313 running on transmission 1.72. I can download to about 2GB done and then it just fluctuates. I stop or remove other torrents and it seems that helps and now it can reach about 2.5GB complete out of 3.8GB. But the problem returns, i.e. hovers around 2.5GB downloads completed. Any ideas? I can send you the torrent to see if you encounter the same problem.
Alex,
Try torrents like openoffice or ubuntu see if it completes. It could be issues with torrents instead of transmission.
epiphanius
how to do a whitelist to all ip?
andy
if its the torrent problem, why is it that i don’t encounter the problem with the same torrent when i download it on my pc using utorrent?
fishball,
The number of seeders/peers you connect to in transmission is much lesser than the number you connect to in PC. Try to download only 1 torrent at a time and it may complete.
The NAS is an underpowered device (limited memory and cpu resource) hence you cannot assume it will connect to that many peers to complete a single torrent. In P2P, the files are actually chopped into parts and whether you can complete the torrent depends on whether the peer you connect to have the part you want. Hence, a full fledged computer may connect to 100 peers effortlessly and hence have a greater chance of forming the complete torrent. On the other hand, a NAS might not have the resource to connect to that 100 peers at one time to complete the torrent.
Hope it helps.
andy,
thanks for your help.
Dear shadowandy,
can You please give me an information how loud DND-343 can be?
I was reading on the Synology summary page(http://www.synology.com/enu/products/compare_spec.php), that the concurrenting product to my DNS-343 (the DS-409) should be around 23 dBa. How loud goes the D-Link product, if You know about?
Many many thank in advance!
Tamas, from Germany, Munich
vasgyuszi,
I think you have to search online for the information.
Dear shadowandy,
that’s the point why I’m asking you, because I didn’t found any information/test/review about the loudness of this product.
Thanks,
Tamas
vasgyuszi,
I think you can obtain such information through D-Link or find someone with testing equipments to measure the loudness of the unit during operations.
Absolutely fantastic !! Thanks
the lines -
Setting the download directory
1. Type the command “su nobody -c “mkdir -p /mnt/HD_a2/transmission-downloads”“
came back with a error message but I just created the folder myself and it’s up and running.
Was using the BT prog that comes with the DNS-323 but most torrents it wouldn’t add due to — invalid torrent ?
So used your prog & setup and now all happy.
Also added the port 51413 (found in the transmission settings file) to my Router and now downloads coming in & sharing at great speeds ..
Once again Thanks !!
vasgyuszi,
Regarding the “loudness” of your DNS-343 -
If your talking about the fan being on all the time making the noise, d-link has new firm-ware for some models that will stop or slow the fan down depending on temperature.
My DNS-323 fan was always going full bore when i set it up, til i added the latest firm-ware, now it turns it’s self off most the time – much quieter.
Hi ShadowAndy,
Is there any links where I can uninstall everything, e.g funplugz, transmission, etc. Think I have made a mess but I do not want to format my HDD with data on it. Wanna a cleanboot and start all over again…
Thanks.
Hi ShadowAndy,
I have problem in downloading torrent using transmission. I know I followed each steps of the instructions in installing transmission. I have not encountered problem except not being able to download. I tried using Vuze and successfully downloaded that same torrent to ensure the torrent is working.
Please help me also in resolving this. Thanks…
rootsntips,
What is the error message you got?
ShadowAndy,
I don’t see any error message on the screen. Do you know where I can check it?
Hi Andy,
I have a query here, right now, I’m using Transmission 1.72 on my Dlink 343.
Would it affect my files and settings on the downloadings if I upgrade to Transmisssion 1.74? I have two 1TB set to JBOD.
Zed
Zed,
It shouldn’t affect your files.
Hi Andy,
Thx. I have already upgrade it. Everything seems working. So with this funplug, any upgrading would not affect the rest right? for example, if I’m going to add another 1TB to the current two 1TB hdds? Thx again.
Zed
rootsntips,
There is a transmission log file. You need to telnet/ssh to view it.
Transmission 1.76 is available. Is it possible to update this guide?
Thanks.
Zed
Zed,
Updated the guide.
Hello Guys and Girls,
Could somebody be so kind and send me the Transmission-1.76-1.tgz binary?
Unfortunately Kylek’s site is not working lately and the dns-323 version is nowhere else to be found on the web.
Thanks in advance
T
toxxiq at gmail dot com
toxxiq,
I don’t face problem with the site. Do check your connection.
Hi Andy,
I’m stuck with this “wget: bad address ‘www.inreto.de’”
the site is down?
alvin,
I can access the site. Do check your connection.
andy,
I suspect is my dns 323 not connecting to the internet cause the built in BT is no working as well. Was using Starhub before changing to Mio. Any idea about 2wire firewall?
Andy,
i managed to figure the problem but now come this:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you’re editing settings.json, see the ‘rpc-whitelist’ and ‘rpc-whitelist-enabled’ entries.
If you’re still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.
Alvin,
It is mentioned in the guide under the section Updating the whitelist.
Andy,
I already followed the guide.
“rpc-whitelist”: “127.0.0.1,192.168.1.*”,
“rpc-whitelist-enabled”: true,
and this is the only error i remember:
/mnt/HD_a2 # sh /ffp/start/transmission.sh start
Starting transmission-daemon
/mnt/HD_a2 # su nobody -c b mkdir -p /mnt/HD_a2/transmission-downloads
bmkdir: No such file or directory
Alvin,
make sure u type the command as mentioned in the guide.
Problem with permissions, here is what transmission-daemon.log reads
“/ffp/bin/transmission-daemon: Permission denied”
permissions for transmission-daemon are 0777
my download folder is 777
settings.json 644
transmission-daemon.sh 777
can’t figure out what part of the system is complaining about permissions.
the ownership for all files is nobody:501 (not sure what 501 group is, or it matters being that all my files have user permissions)
Any ideas?
Brad,
What are the steps you did to install transmission?
Hey shadowandy, I used the above guide. I’m all fixed now…
still couldn’t track down the permissions issue, so I funpkg -r Curl + Transmission then installed again, this time no permissions issue. Very strange.
Hi Andy,
Firstly a big thank you for the wonderful guide.
i am having the same problems as Ginch.
i dont see any download folder created in my drive even thru i follow your guide.
read your answer as “Make sure the folder is writable by transmission (nobody)”
how to i created the folder to be read by tranmission?
i have try creating the folder but it still give me the same error
appreciated the help
acid
Thanks for the guide!
Got Transmission up, but not running exactly… Being a Linux illiterate, I’m not sure what’s meant by /mnt/HD_a2/ ?
The 323 is mapped as drive X in WindowsXP so I guess I’m not seeing the same names as in Linux. I’ve used this to set the download folder – transmission-remote 127.0.0.1 -w /mnt/HD_a2/Downloads – and it reported success, but the web gui still says “no such file or directory”. I set the same location in the web gui preferences.
Where should I have that folder? At the moment it’s in the root of X. Is that right?
Ginch August 5th, 2009 at 7:03 pm
acid,
The folder should be created in Volume_1\ and writable by the transmission process. If you follow the guide, the downloads will all be at transmission-downloads folder in Volume_1
hi andy,
i have it figure out after i change the web gui preference
from mnt/HD_a2/transmission-downloads
to mnt/HD_a2/downloads
once again thanks for the guide
Hi,
I’ve installed transmission 1.76 and have downloaded a few files with it already. I’ve restarted it not too long ago and now, i can’t access it by remote gui or by internet browser (connection timed out).
When I look at the settings.json, the configuration is fine. But when I use “transmission-daemon -d”, it doesn’t show the same configuartion as settings.json, it looks like a default configuration.
I’ve found out that the config file used when launched by :
/ffp/start/transmission.sh start
is in fact in the root user home directory :
/home/root/.config/transmission-daemon
chiny,
I am using 1.76 (the one in the link). The transmission home still points to /mnt/HD_a2/.transmission-daemon. It only changes to /home/root/.config/transmission-daemon if you invoke transmission-daemon manually (e.g. transmission-daemon -d) without using /ffp/start/transmission.sh
Hope you realized you have unintentionally start transmission without using transmission.sh and hence it doesn’t read the settings.json as mentioned in the guide.
Yeah, I’ve figured it out.
But when I start transmission manually, I was able to access the webGUI and the remote gui.
I solved my problem by deleting the content of “/mnt/HD_a2/.transmission-daemon/resume”
Once started, I was able to access the GUI and transmission verified every torrents I had.
Hope this will help someone else ^^
[...] for this D-Link NAS. * Disclaimer: This guide is essentially following Shadowandy’s guide: here, with update for newer version of Transmission version, and written in my own space for my [...]
Hey, can anyone hit kylek.is-a-geek.org? I’ve been trying to download curl-7.18.1.tgz and Transmission 1.83 all day and can’t get through:
/mnt/HD_a2 # wget http://kylek.is-a-geek.org:31337/files/curl-7.18.1.tgz
Connecting to kylek.is-a-geek.org:31337 (91.14.141.127:31337)
wget: cannot connect to remote host (91.14.141.127): Connection timed out
The DNS-323 seized up on me so I did a reboot, and somehow lost all of my settings. Weeks of downloads may be lost! After editing the settings.json file I got hit with the dreaded “No such file or directory”.
I’m unable to download these two files for a reinstall. I can’t even hit the website with a browser.
Anybody else able to hit it?
Had a bit of a crash yesterday, but it’s now resolved. I post what happened here in case anyone else runs into it.
It started with Transmission acting up. Under each file in the list was the error “Too many files open”. I rebooted the DNS-323, but that seemed to make the situation worse. Once I finally got the device back up, all of my torrents were showing “No such file or directory”. Going to my download folder via Explorer showed that the files were still there, but Transmission didn’t like them. All torrents, including completed ones, were showing 0% completion.
To make things worse, I can not download from kylek.is-a-geek.org, so upgrading Transmission is out of the question for now.
settings.json was ok, as well as ports, bandwidth, yada, yada, yada. Everything should be working, but I had a dozen frozen torrents. I could not “verify local data”. Any attempts at Resuming the transfers would give the appearance of working for about ten seconds, then go back to “No such file or directory”.
Playing with ownerships, groups, permissions, etc. via Telnet got me nowhere.
Apparently I’m not the only guy who has had this problem, but unfortunately the fixes I found online didn’t help anything.
I did find, however, that I could add a new torrent and it would transfer fine. So Transmission is still working, just existing torrents are frozen.
Long story short, using ls -la via Telnet showed that the frozen torrents had the same permissions as the working new torrents. However I could not delete the frozen torrents from the download folder. I could copy them out without any problems, and work with the copies on my XP client.
After tearing through various forums (where would we be without Andy and Kyle?), I was able to get my torrents running again by:
1) finding the .torrent files in \.transmission-daemon\torrents then copying them to my client’s desktop
2) going through the torrent list in Transmission and doing a “Remove from List” for each frozen torrent ( -not- “Trash Data and Remove from List”)
3) Opening up each of the .torrent files from the desktop in Transmission and re-adding the torrents to the list. When you do this, you should see “Verifying local data” as Transmission sees the existing partial downloads.
Right now I’m waiting for the “verifying local data” to run its course, but so far it looks good. If anything new pops up, I’ll report back here.
Hi Cranky,
For the part on not able to connect to remote host, you got to check your Internet connection. Noticed that some users are not able to connect to non-standard ports (e.g. port 31337/tcp instead of 80/tcp).
Hope your method of removing .torrent then re-adding them solves your hanging issue. For me, I simply deleted the settings.json file, ran transmission. The hanging went away.
Thanks for your advice on the hanging issue, Andy. I have a knack for finding the long way to do simple tasks…
As to downloading from Kyle, strangely enough it just started working for me this afternoon, just as I was about to check my ports on my router. Weirdness!
I managed to download and upgrade, so all is working great now. Thanks for your help.