Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I upgrade Transmission 2.22 to 2.42 on my dns-320, but i have a problem: The webui not works correctly. It shows the the torrents, but i can't start it by the resume button on the top and the little button next to the torrent. The right-click menu is works. The paused torrents's status bar is green not gray.
Offline
The problem solved. Chrome browser loaded the old webui from cache. I cleaned the cache it's work correctly.
Offline
Getting some scrape error on some trackers with 2.42 had to revert to 2.32
Running on a DNS-323 and tested in Chrome and Firefox (Cleaned Cache)
Last edited by fab (2011-10-31 05:36:41)
Offline
Any mirrors for the lastest transmission package? KyleK's server seems to be down.
Offline
The server is up and running.
Offline
KyleK wrote:
The server is up and running.
Weird, I'm still getting connection timed out error
Offline
Please note that the webserver uses a non-standard port, which might be blocked by your router and/or firewall.
Offline
KyleK wrote:
Please note that the webserver uses a non-standard port, which might be blocked by your router and/or firewall.
Seems so, managed to d/l it from another network location. It's weird that I've been d/l'ing older versions succesfully in the past from home. Thanks for keeping this updated!
Offline
I notice performance degraded seriously with transmission running as below
I only have 100mbps switch between
Running warmup...
Running a 400MB file write on drive Z: twice...
Iteration 1: 6.06 MB/sec
Iteration 2: 6.2 MB/sec
------------------------------
Average (W): 6.13 MB/sec
------------------------------
Running a 400MB file read on drive Z: twice...
Iteration 1: 4.87 MB/sec
Iteration 2: 5.42 MB/sec
------------------------------
Average (R): 5.15 MB/sec
------------------------------
After killing transmission the speed below. Anyone know how to fix this.. i dont want transmission to slow down my file copy.. I going to get a Gigabit switch for it.
Running warmup...
Running a 400MB file write on drive Z: twice...
Iteration 1: 9.02 MB/sec
Iteration 2: 9.02 MB/sec
------------------------------
Average (W): 9.02 MB/sec
------------------------------
Running a 400MB file read on drive Z: twice...
Iteration 1: 8.16 MB/sec
Iteration 2: 8.12 MB/sec
------------------------------
Average (R): 8.14 MB/sec
------------------------------
Offline
FIXED!
I appear to have installed and setup Transmission correctly, and I set the daemon to accept connections from 192.168.*.* but I still get the message when I got to http://DNS-IP:9091/
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.
I'm connecting from another computer on the same network so I don't know why I can't connect.
Is there a way to read the settings file to make sure I'm actually setting the permissions properly?
Setting up funplug is about the extent of my knowledge on linux command line operations, so detailed commands would be very helpful.
Thanks.
I just checked the ffp.log and found this.
Couldn't read "/mnt/HD_a2/.transmission-daemon/settings.json": Permission denied Couldn't open "/mnt/HD_a2/.transmission-daemon/transmission-daemon.log": Permission denied
I had entered the commands to fix this as I was going along with the tutorial in the OP, but I guess I had done something wrong.
So I did it again and restarted the whole device, that seemed to have fixed it.
Last edited by UberSprode (2011-11-11 02:25:23)
Offline
I thought I'd let you guys know: The Transmission team is looking for a graphics designer who'd be interested in giving the Transmission web interface a ... facelift
So if you got some skills in that regard (or know someone who does), and want to earn some open-source cred, give it a try!
Since the project is open-source, all you gotta do is to spruce up the existing webUI and post the results to the Transmission forums or their bug tracker.
Cheers!
Offline
Kylek link seems down (times out) and sharks' mirror's file fails to extract (invalid gzip magic)
Offline
Sorry for the outage. The files should be accessible again now.
Offline
on my NAS /mnt/HD_a2 does not exist, only /mnt/HD/HD_a2
so
$ su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_a2/Downloads -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*"
should be replaced by
$ su nobody -c "transmission-daemon -f -g /mnt/HD/HD_a2/.transmission-daemon -w /mnt/HD/HD_a2/Downloads -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*"
Offline
hello
in which directory have I to put the blocklists's files
and in which format?
(ex : file : nipfilter.dat.gz)
thnaks a lot
Offline
Transmission keeps my drives awake, even when not dling or seeding any torrents. Anyway to prevent transmission from keeping my drives awake?
Offline
The easy answer is to move funplug (or at least Transmissions settings folder) to a USB stick.
The longer answer is to ask the Transmission devs as to why it keeps your disk awake.
Offline
KyleK wrote:
The easy answer is to move funplug (or at least Transmissions settings folder) to a USB stick.
The longer answer is to ask the Transmission devs as to why it keeps your disk awake.
I have a UPS plugged into the usb port so that is a no go. Anyone else have the same problem as I?
Offline
My drives power down after inactivity. I have a feeling your box is still getting pinged by trackers which cache your IP address. My router blocks all unsolicited incoming packets. Is it possible your box is exposed to the incoming requests?
Offline
joligario wrote:
My drives power down after inactivity. I have a feeling your box is still getting pinged by trackers which cache your IP address. My router blocks all unsolicited incoming packets. Is it possible your box is exposed to the incoming requests?
How could I check if it is or isn't?
Offline
leech1980 wrote:
Transmission keeps my drives awake, even when not dling or seeding any torrents. Anyway to prevent transmission from keeping my drives awake?
I'm in the same boat after updating from 2.22 to 2.42
I noticed the only new features are the µTP support and UDP tracker support, maybe disabling that can yield some progress?
I disabled µTP throught Transmission Remote GUI to see if that helps, I'll get back to this thread in a day.
Last edited by overthinkingme (2011-12-21 04:59:54)
Offline
Are you 100% sure it is Transmission that is keeping the drives awake? Mine hybernate.
Offline
Hi Everybody, Hi Kylek,
I'm using very long time ago the versions of Transmission. I upgraded now to version 2.42. It is working fine, just I have "memory leakage" problems. After few days slows down my NAS. When I'm checking memory and CPU usage with top, than memory usage are at 76% CPU at 20% after few days, and direct after restart of the daemon memory: 235 CPU at 30%. After these few days needs Transmission remote more time to connect to the daemon too.
With the earlier version (ver: 2.22) I had to restart about every or every second week. I didn't upgrade it yet, because with ver. 2.30 I had the same symptom.
I have normally about 100 torrents in the list, and from these are about 50~60 seeds.
Did somebody have similar problems?
Could I turn off somhow the logging of daemon with modification of start script?
Last edited by charlie (2011-12-21 23:50:25)
Offline
There are currently no known memory leaks in Transmission, as far as I know. The memory increases, because Transmission saves information about torrents and trackers (peer info, for example) in memory for each torrent.
It's been always my opinion that the DNS-323 with its measly 64MB of RAM is not suited for hosting that many torrents.
You can try and disable some features (UTP, DHT, PEX, LPD), but I cannot say if that will have any impact on the memory footprint.
$ transmission-remote --no-lpd --no-dht --no-pex --no-utp
Please note that this will likely come with a degrade in download speed, as Transmission won't find as many potential peers as before.
You can also opt to prefer unencrypted peer connections, which might help with performance a bit:
$ transmission-remote --encryption-tolerated
Logging to a file can be disabled as well, but it won't do anything memory- or performance-wise.
Edit the startup script for this and remove the "-e ${TRANSMISSION_LOG}" part.
Offline
I'm experiencing a similar thing to what Charlie reported.
I've starting to investigate it by setting up a build env (ffp)
I've set the configure options as following:
--prefix=$CPREFIX --disable-cli --disable-gtk --disable-nls --without-inotify
And for libevent:
--prefix=$CPREFIX
Kylek, are these the options you use when you compile Transmission?
Offline