Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I suggest downloading the files directly on the device, using the wget command.
Maybe OS X does something to the files when copying them over, I dunno.
Offline
Hey anyone of you ever have problems with 1.33 not allowing you to open torrents from the web interface? Mine seems random, sometimes it uploads and saves fine and others it just dies (literally, the process crashes). The whole thing is very random and pretty annoying because if I have some large torrents downloading and I try to add more it may or may not crash which forces me to restart the process (and then takes forever to recheck the files).
Any ideas?
Offline
I can't say I've experienced something like that, but in any case I suggest you simply update to v1.34. Should be simple enough (download, funpkg -u <file>), and it might fix it.
Offline
I just did. It still happens.
Offline
KyleK wrote:
I suggest downloading the files directly on the device, using the wget command.
Maybe OS X does something to the files when copying them over, I dunno.
Worked!
Thanks a bunch
Offline
I'm using Transmission on my CHS3NAS for some time now. All works ok, but my torrents are pretty slow. I know finding the cause of slow torrents can be pretty complex, so here is a list of things I already did.
- Checked the portforwarding on my router
- Tried different routers (Airport Extreme and Sitecom ADSL)
- Tried different ISP's (I have both UPC cable (24/2Mbit) and TweakDSL (8/1Mbit))
- Tried a different (non-default) poort
- Tested with encryption on and off
- Checked loads on my CHS3NAS using top (about 40% IDLE)
- Limited upload at 80%
- Switched off all other computers on the network
So what speeds are you guys getting using Transmission on your NAS? I'm getting only about 20-50 KB/s per torrent. When I used my iMac for running Transmission my downloads where about 10 times faster by average.
When I was running Transmission on my iMac it was stil at 1.2x. Could it be that Transmission is slower since the 1.3x release?
Last edited by Fevida (2008-09-27 13:01:56)
Offline
The download doesn´t start:
root@CH3SNAS:/mnt/HD_a2# transmission-daemon -f
Transmission 1.34 (6794) started
Serving the web interface files from "/ffp/share/transmission/web"
open_listening_port(9091): Address already in use
cannot open port 9091
Here is the transmission-daemon.log:
Transmission 1.34 (6794) started
Serving the web interface files from "/ffp/share/transmission/web"
Loaded 1 torrents
Port Forwarding: Opened port 51413 to listen for incoming peer connections
openSUSE-11.0-GNOME-LiveCD-i386-iso: Got 50 peers from tracker
Couldn't create "//openSUSE-11.0-GNOME-LiveCD-i386-iso": Permission denied
What´s going wrong?
Offline
Transmission can't create the folder where it's supposed to download the file. You have to set the environment variable TRANSMISSION_HOME to a path of your desire. The default is /mnt/HD_a2/.transmission-daemon, and this will be set when you use the transmission.sh startup script. If you run Transmission by hand (as in your above example), you also need to set the variable by yourself.
(On another note: it seems port 9091, which is used for inter-process communication, is already used by something else. You can set a different port on startup using the command "transmission-daemon -p <port number>" (see "transmission-daemon help" or "man transmission-daemon" for more information).
Offline
Hi all! Could somebody be kind enough the step by step instructions on how to install Transmission 1.33+ on DNS 323
I have searched the net and the posts here and I can't seem to find any detailed ones. I have got it to work initially, but for some reason downloading torrents now give out "Permission Denied" errors
my torrent download folder is /mnt/HD_a2/DOWNLOADS and is owned by nobody:501
the /mnt/HD_a2/.transmission-daemon is owned by nobody:501 as well
Again, I could download torrents before just fine..it just stopped working.
Any help or the detailed instructions perhaps so I could start all over.
Thanks!
Offline
Check out posts #56 and #57 of this thread where someone else had the same problem. The solution might fix it for you.
I'm not a friend of the "run as nobody" solution, because it seems to cause problems for people. I use a specific user account name (my own) for this. This has the positive side effect that only I may delete files from the download directory.
Offline
Clutch doesn't seem to save my settings and I have no settings.json file... any ideas?
Offline
Great stuff Kyle. However for those of us who have existing torrents and want to see them running in the new version after upgrading, you will need to copy them across to the new config directory:
cd /mnt/HD_a2/ cp .transmission/torrents/* .transmission-daemon/torrents/ cp .transmission/resume/* .transmission-daemon/resume/
Restart transmission if it is already running.
As for speeds and number of torrents, I routinely have 5+ torrents open and have seen total download speed exceed 800KB/s. The NAS is capable of high speed downloads, so if you aren't getting the speed you think you should be (i.e. verified same torrent using a computer on same connection) then you have a problem that I can't begin to imagine how to solve.
Offline
I don't think upnp port forwarding is working properly with Transmission 1.34 on DNS-323. Even though the log file appears to indicate that it is working properly, the default port 51413 is not shown as available from outside my network.
Offline
Just discovered they removed the ability to upload a new torrent via a URL directly in clutch (I upgraded from the 1.2x series). Annoying.
Last edited by Muppet (2008-10-12 02:40:56)
Offline
I know what you mean. I was quite disappointed about that as well. charles even said it's unlikely it'll get integrated back anytime soon.
It has to do with the new JSON RPC interface.
Offline
Is this mirrored anywhere? KyleK's website is unreachable...
Offline
Website is up again.
Offline
Hi Folks!
Thanx for this perfect guide for Transmission.
But I'm totally newbie so please tell me, what is the next step if I succesfull install the Transmission without
errors.
So how can I download torrents, has it any grapichal interface?
Thanks for your help, Best Regards:
C.
p.s. When I finished the installation of Transmisison the original BT client in the DNS-323 no longer working. Is it
correct?
Offline
Hi,
Host website is down again lah. Will mirror it when it goes back up if it is ok with Kyle.
Dom
Offline
That must have been a glitch on your end. The server has been up for the last 24 hours.
It's working fine now as well.
Offline
Hi, and thanks again for your work. I have three little questions :
1/ I sarted too many transmission-daemon and I would like to stop some of them :
/ # ps aux|grep transmission-daemon 21706 root transmission-daemon -b 21707 root transmission-daemon -b 21708 root transmission-daemon -b 21751 root transmission-daemon -B 21752 root transmission-daemon -B 21753 root transmission-daemon -B 21794 nobody /ffp/bin/transmission-daemon -f 21795 nobody /ffp/bin/transmission-daemon -f 21796 nobody /ffp/bin/transmission-daemon -f 21800 root transmission-daemon -b 21801 root transmission-daemon -b 21802 root transmission-daemon -b 21808 root grep transmission-daemon
I want to kill the -b and -B. How can I do this ? (I tried the command "kill pid" but no effect).
2/ I want to enable blocklist : how can I do this? (I copied the level1.txt into blocklist dir and start transmission-daemon -b but no effect : when I nano the settings.json, blocklist enabled is on 0)
3/ About settings.json, how can I modify the "max_peers" ?
Thank you in advance ...
Offline
1. Did you try the 'kill' command for each of those processes (PIDs)? One is always the main application which spawns new processes when started. Try "killing" the smallest PID of each triplet.
If that doesn't work, you'll have to kill all of them using 'killall transmission-daemon' or 'sh /ffp/start/transmission.sh stop'
2. the settings file is only saved upon shutdown of Transmission, so you won't see a change there. Check the .transmission-daemon folder for a logfile and look if it contains anything about the blocklist being enabled. (Actually, I'm not sure logging is enabled by default, if not you can enable it in /ffp/start/transmission.sh)
3. You can modify settings.json with a normal text editor, but only when Transmission is not running. Quit transmission-daemon, edit the file to your likings, and start it again.
Most of the settings can also be changed at runtime using transmission-remote (type 'transmission-remote --help' or 'man transmission-remote' for specific information).
Offline
Thank you.
I didn't achieve to stop transmission-daemon with the kill command. So I reboot and they have been killed .
I edit settings.json succeffuly. So I enabled blockpeer list and limit max_peers to 50. I also edit the transmission.sh : I add -b option to the transmission_start paragraph.
Thank you again.
Offline
I have a little problem with my last transmission.sh edit :
First, here is my transmission.sh edit : I just add "-b" to the start paragraph (just above the "-f" option) in order to enable blocklist option at startup.
Here is a ffp.log before the edit :
**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) **** Tue Oct 14 19:00:43 GMT 2008 ln -snf /mnt/HD_a2/ffp /ffp * Running /ffp/etc/fun_plug.init ... * Running /ffp/etc/rc ... * /ffp/start/syslogd.sh inactive * /ffp/start/SERVERS.sh inactive * /ffp/start/portmap.sh inactive * /ffp/start/unfsd.sh inactive * /ffp/start/transmission.sh ... Starting transmission-daemon * /ffp/start/cleanboot.sh ... Setting up cleanboot... * /ffp/start/nfsd.sh inactive * /ffp/start/ntpd.sh inactive * /ffp/start/LOGIN.sh inactive * /ffp/start/telnetd.sh ... Starting /ffp/sbin/telnetd -l /ffp/bin/sh * /ffp/start/sshd.sh inactive * /ffp/start/rsyncd.sh inactive * /ffp/start/mediatomb.sh inactive * /ffp/start/kickwebs.sh inactive * /ffp/start/lighttpd.sh inactive * /ffp/start/inetd.sh inactive * /ffp/start/fanctl.sh ... * OK
Here is a ffp.log after the edit:
**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) **** Wed Oct 15 21:20:27 GMT 2008 ln -snf /mnt/HD_a2/ffp /ffp * Running /ffp/etc/fun_plug.init ... * Running /ffp/etc/rc ... * /ffp/start/syslogd.sh inactive * /ffp/start/SERVERS.sh inactive * /ffp/start/portmap.sh inactive * /ffp/start/unfsd.sh inactive * /ffp/start/transmission.sh ... Starting transmission-daemon Transmission 1.34 (6794) started Port Forwarding: Opened port 51413 to listen for incoming peer connections Blocklist "level1.bin" updated with 222644 entries Blocklist "level1.bin" contains 222644 entries Serving the web interface files from "/ffp/share/transmission/web" Blocklist "level1.bin" contains 222644 entries Loaded 5 torrents
And that'all ! Transmission work great but no telnet, no fanctl or cleanboot ... I can't modify settings.json or transmission.sh because telnet is not running...
How can resolve this problem ?
Thank you in advance.
Last edited by lekeur (2008-10-15 22:48:51)
Offline
You must've changed something more in the startup line than add '-b', otherwise this wouldn't happen.
You can modify your startup script and remove execute permission from /ffp/start/transmission.sh:
#add the following line before the block that says "# run commands" /ffp/bin chmod -x /ffp/start/transmissions.h # run commands if [ -x $FFP_RC ]; then echo "* Running $FFP_RC ..." $FFP_RC echo "* OK" else echo "$FFP_RC: Not found or not executable" fi
When you got access back to telnet, post the line you changed in transmission.sh
Btw, I think you only need to specify the -b command once. Transmission should remember the setting (see settings.json)
Last edited by KyleK (2008-10-16 00:08:49)
Offline