Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I just did a complete new clean installation of the fun_plug with the new Transmission 1.91 working like a charm, except for the funcionality of the watch-dir I never used before: it only updates at the starts of transmission, then for a while, then not anymore... Is there an update interval for the watch-dir to work? Or should I ask this in the Transmission Forums? Here is part of my logfile where everything seems ok, it finds the new torrents, but when I add one now in the watch-dir, it isn't working:
[16:44:58.892] Transmission 1.91 (10269) started (session.c:615) [16:44:58.893] RPC Server Adding address to whitelist: *.*.*.* (rpc-server.c:772) [16:44:58.893] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:945) [16:44:58.894] RPC Server Whitelist enabled (rpc-server.c:949) [16:44:58.894] RPC Server Password required (rpc-server.c:952) [16:44:58.894] External Done Command set to: (null) (session.c:828) [16:44:58.895] External Done Command enabled: no (session.c:848) [16:44:58.895] DHT Reusing old id (tr-dht.c:365) [16:44:58.896] DHT Bootstrapping from 46 nodes (tr-dht.c:146) [16:44:58.896] Using settings from "/mnt/HD_a2/.transmission-daemon/" (daemon.c:422) [16:44:58.896] Saved "/mnt/HD_a2/.transmission-daemon/settings.json" (bencode.c:1644) [16:44:58.897] transmission-daemon requiring authentication (daemon.c:426) [16:44:58.897] Watching "/mnt/HD_a2/_Downloads/_Torrents" for new .torrent files (daemon.c:438) [16:44:58.898] Using readdir to watch directory "/mnt/HD_a2/_Downloads/_Torrents" (watch.c:138) [16:44:58.898] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67) [16:44:58.898] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67) [16:44:58.899] Loaded 13 torrents (session.c:1693)
Last edited by Frans (2010-03-08 12:09:11)
Offline
The watchdir is scanned about every 10 seconds.
Does the file you added to watchdir have the extension ".torrent"? This was a change between 1.90 and 1.91, I believe: Before, Transmission would simply add every file, now it only adds files which end in ".torrent". Even ".torrent.bak" or such cases won't work.
Offline
They all end with ".torrent". I don't think ".TPB.torrent" will be a problem? Is there anything I can do to check where the problem occurs? Debugging of somekind? Can it be a ownership problem? Transmission runs under "Frans", same as the user login owner so I can edit/delete the files. All directories that Transmisison uses are owned by "Frans".
EDIT
It appears to be working to find the new torrent files in the watch folder (also changed directory in settings to "\/torrents\/" with extra slash at end) when I see this:
[05:45:05.015] Found new .torrent file "particular_torrent.4597849.TPB.torrent" in watchdir "/mnt/HD_a2/_Downloads/torrents" (watch.c:195)
But this torrent wasn't added to the downloaded torrent folder like this one (and doesn't show up in GUI, it only sees it...):
[05:55:02.161] Found new .torrent file "another_particular_torrent.4716800.TPB.torrent" in watchdir "/mnt/HD_a2/_Downloads/torrents" (watch.c:195) [05:55:02.161] Saved "/mnt/HD_a2/.transmission-daemon/torrents/another_particular_torrent.fcb7957dd75c92d9.torrent" (bencode.c:1644)
Looks like random? Weird...
EDIT 2
There appears to be something different going on. After a while, Transmission stops logging (same time it doesn't load new torrens in watch folder). Adding a torrent through web-GUI works. When I dump the settings though ("transmission-daemon -d") I get the standard settings!
... "download-dir": "\/home\/root\/Downloads", "encryption": 1, "external-done-command": "", "external-done-command-enabled": false, "incomplete-dir": "\/home\/root\/.config\/transmission-daemon\/Incomplete", "incomplete-dir-enabled": false, "lazy-bitfield-enabled": true, "message-level": 2, ... etc
Don't know if this is weird or anything, but I do believe it is weird that the logging stops after a short period...
Last edited by Frans (2010-03-08 19:43:20)
Offline
Well I tried everything but it appears that the watch-dir is functioning properly for a short period of time (at least a couple of minutes when Transmission has started). When later on I add a .torrent file in the watch-dir it isn't picked up and at the exact same time logging stops (no more log-messages after that). Seems like a bug?
Offline
I'll try to test the watchdir function, but I don't know when I've got the tme. I'll let you know how it goes.
Offline
I have configured everything as written in the first post and everything is working except for one thing.
When I try to delete a torrent and it's file it does not get deleted, neither through the remote GUI nor through windows. (The only way I can delete it is if a connect through telnet onto the device and delete it through Linux)
When I try to delete through windows I get the following: You require permission from Unix User\nobody to make changes to this file...
is there any way I could solve the problem? Can I make the default user myself? or if not give permission to everybody when creating such a file?
thanks in advance.
szsz
Offline
Clicking "Remove torrent" in the Transmission Web GUI will only remove the torrent from Transmission itself, it will not touch the downloaded data.
You can right-click the torrent and select "Trash data & remove from list...". This will remove the torrent from Transmission and also delete the files on disk.
If you want to delete through Samba (from Windows for example), Transmission must be running either as user "nobody", or as the user you're logging in through samba. You can change the user Transmission is running as directly in the /ffp/start/transmission.sh startup script. Just open it with a text editor (not Windows notepad though!) and change the variable "user".
(btw, it should automatically run as user "nobody").
Offline
szsz, just set "umask" in settings.json to 0 and you will get all needed rights to dance with downloaded via transmission files.
Last edited by Isildur (2010-03-12 00:59:51)
Offline
I can't download the Transmission package from here "http://kylek.is-a-geek.org:31337/files/Transmission-1.91-1.tgz", it keeps telling me it can't find the route. Anyone else having that problem? Can someone post up the files used in this?
Offline
Isildur wrote:
szsz, just set "umask" in settings.json to 0 and you will get all needed rights to dance with downloaded via transmission files.
thank you! that solved the proplem.
szsz
Offline
Registered to be able to post some feedback along with kilothanks to everyone, especially KyleK, who made Transmission possible on my DNS-323 (v.B1).
I recently (yesterday) installed and have been using the latest Transmission (1.91) without any issues that I can spot, by following this thread's post #1 directions.
I just wanted to add that, being a believer in keeping systems updated, I got the latest Fonz repo curl package, now at version 7.19.4-1, which I installed without any troubles that I could spot.
(see http://www.inreto.de/dns323/fun-plug/0. … 19.4-1.tgz)
I have since upgraded curl to Uli's repo version, which is now at 7.20.0-1, and everything's still dandy.
(downloaded from http://ffp.wolf-u.li/additional/net-mis … 20.0-1.tgz and used 'funpkg -u curl-7.20.0-1.tgz')
After searching the thread, I found no mention of curl updating apart from TylerD004 inquiry at post #740, so maybe post #1 could be updated to reflect this -- if KyleK sees fit.
Last edited by pnin (2010-03-12 18:38:21)
Offline
I had just set up transmission and got it running
my completed downloads files are delete from the Downloads folder upon completion?
anyone can help me out here?
Offline
I'm using the latest transmission and when I tried downloading files of thdbits I get a message stating that I'm using a banned client.
When I checked their rules, they allow Transmission 1.2 and above.
Could it have been an error on my installation or thdbits' system?
Offline
noen98 wrote:
I had just set up transmission and got it running
my completed downloads files are delete from the Downloads folder upon completion?
anyone can help me out here?
Did you specify separate folders for Downloads and Incomplete files? Transmission will then move files from one folder to the other upon completion. Check the logfile.
Offline
beefy314 wrote:
I'm using the latest transmission and when I tried downloading files of thdbits I get a message stating that I'm using a banned client.
When I checked their rules, they allow Transmission 1.2 and above.
Could it have been an error on my installation or thdbits' system?
Not knowing the site I can't be 100% sure but I would assume that they don't allow some versions of transmission for some reason. It is not something you can influence with your configuration.
Please ask them specifically why they ban your version of Transmission and let me or the Transmission devs know.
Offline
According to the moderators(THDbits.org) Transmission 1.2 and above is supported. They said transmission 1.90 on ubuntu is working and suggested that i reinstall the program which I did but I still get the same error
Is the Transmission for the dlink same as for ubuntu?
These are the clients allowed and they were asking what kind of linux system is on the Dlink
Linux:
* Azureus: 2.5.0.4, 3.0.5.0, 3.0.5.2 and later versions
* Deluge: 0.5.9.1, 1.1.6 and later versions
* Rufus: 0.6.9, 0.7.0 and later versions
* Transmission: 1.21 and later versions
* rTorrent: 0.8.0(with libtorrent 0.12.0 or later) and later versions
* Enhanced CTorrent: 3.3.2 and later versions
Last edited by beefy314 (2010-03-14 12:01:16)
Offline
The D-Link runs Linux 2.6.12 afaik.
I use the same source code for Transmission for the D-Link package as someone would for the Ubuntu version, so feature-wise there is no difference.
That error message you get is a response from the tracker. It is nothing within Transmission itself.
Every time Transmission announces itself to a tracker it sends a user agent string and a peer ID.
The user agent string of Transmission 1.91 is "v1.91", the peer ID is "-TR1910".
Some private trackers - like the one you're using - sometimes blacklist a client, or a specific version of a client, by checking against these two value.
Do you see the error message in the web UI, transmission-remote, or some third-party client? Or all of them?
Offline
On the web ui, I get an error message saying that I'm using a banned client.
So uninstalling and removing it completely then reinstalling won't change anything? Is it possible to get a bad install?
BTW, this is my first time to use this client and it's really nice except for the single site I can't seem to use it with
Offline
No, a reinstall or a bad install have no influence on that particular error message. This is a server-side issue with that particular tracker.
Offline
beefy314 wrote:
On the web ui, I get an error message saying that I'm using a banned client.
So uninstalling and removing it completely then reinstalling won't change anything? Is it possible to get a bad install?
BTW, this is my first time to use this client and it's really nice except for the single site I can't seem to use it with
Transmission 1.90 and 1.91 have been blacklisted by several trackers. Don't know the exact reason, but that's just the way it is. Until a build for 1.92 is available, you could downgrade to 1.7x/1.8x which are probably allowed.
Edit:
reason for the blacklistings: http://forum.transmissionbt.com/viewtopic.php?t=9670
Last edited by Halee84 (2010-03-15 17:15:15)
Offline
1.92 out. Has some fixes.
Offline
You don't say
Offline
Here's v1.92 for you folks.
It fixes a rather nasty issue where downloads are seemingly complete but are really not.
It has multiple other fixes not worth blabbering about, but some changes to the watchdir functionality of the daemon, which might be interesting for Frans to check out.
Let me know how it goes.
Offline
Hi Kylek
I have transmission 1.91 installed. Will my configuration change if I upgrade?
According to the first post these are the commands. Is this applicable to me?
# funpkg -r Transmission-1.22-ffp0.5.tgz (This will remove the old version, but keep all config files intact) ---> Change this to the current transmission i have
# /ffp/start/transmission.sh stop (if you've got an earlier release of Transmission) <--shouldn't I stop transmission before removing?
# funpkg -i curl-7.18.1.tgz (only if you don't have it installed already) <--skip
# funpkg -i Transmission-1.92-1.tgz
# wget http://www.inreto.de/dns323/fun-plug/0. … 9.29-7.tgz <--- i already have this do i need to do it again for the new version of transmission?
# funpkg -i uclibc-0.9.29-7.tgz <-- do I have to do this again?
Thanks Still trying to learn linux
Last edited by beefy314 (2010-03-16 06:44:52)
Offline