Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I am having an issue when I try to copy and paste a .torrent URL into Transmission. I was using v 2.21 and just upgraded today to 2.31
If I copy a URL from a torrent site that is anonymous (doesn't require log in) it seems to work fine. But if I am using a torrent site that requires a username and password, when I try to paste the URL in Open Torrent URL it just sits there and does nothing. Is this normal? If I download the .torrent to my desktop and then click open and browse for the torrent it works no problem and starts immediately.
I am just wondering if there is maybe an area I am missing to provide Transmission with my log in credentials to the website so I can copy and paste URL's directly to the torrents.
Also issue #2, after about 10 minutes of no activity on the transmission webpage 192.168.x.xx:9091 it times out and give me an error to dismiss or details. If i hit dismiss I can get right back in. Is there a setting I should adjust so it doesn't kick me out every 10 minutes?
Thanks in advance.
Offline
mfpockets wrote:
augusto wrote:
Hi everyone.
I started using transmissions a few weeks ago and I've noticed that seeding works fine when I start (or restart) transmissions, but after a few hours it just stops seeding. For example I've downloaded Centos 5.6, and it should have completed a 1.5 ratio in a couple of days, but it has been running for a couple of weeks and it's not near that ratio. I should say too that I'm using v2.31.
On the other hand, if I seed that from my main computer using uTorrent, it starts seeding at full speed in no time.
Has anyone experienced the same problem? I remember reading a post in which someone mentioned that he restarted transmissions ever 12 hours... so I wonder if this is somehow related. Or do I need to tweak the config?
Thanks!Anyone else experiencing this? I just tried this out and it works great but after 30 mins to an hour I notice that all activity stops. If a add a file to download it will work, but previously seeding torrents just say seeding but never any activity. Stoping Transmission and then starting again seems to make the seeding kick in, even if only 5 or 10 kb (private torrent lots of seeds)
Having this issue as well. Just noticed it. I always thought that there were no more leechers and I would remove it from my queue. I tried with a file that had 200+ leechers and after the download completed it seeded for about 5 minutes max before stopping.
Offline
I've been using Transmission + Automatic for a while now, and I love the combination and having torrents on my NAS. However, I see an issue with upload speeds being much slower than they were with uTorrent on my PC.
I've tried various settings, changing global connections, upload slots, etc... but I don't see much of a difference. Is this just differences in the program, or can something be done?
AAAANNNDDD... I just realized that the post right above this is pretty much pointing out the same issue... so it isn't just me.
Last edited by StealthOne (2011-06-16 23:12:17)
Offline
Follow up... Looking on the Transmission forums and there appears to be others having this issue so it appears to be in the Transmission code.
https://forum.transmissionbt.com/viewto … mp;t=11649
KyleK... does this have anything to do with this bug: https://trac.transmissionbt.com/ticket/4260 ???
Last edited by StealthOne (2011-06-16 23:38:08)
Offline
Hello,
I have a DNS-313, but I Decided to upgrade to release 2.31 that Kylek provided. Did all the configuration, and it works....
... but only for limited time: for some unknown reason, after a while, the NAS freezes completly (no telnet, no ssh, no web, no ftp: nothing) to the point I have to power it down, and reboot.
On the transmission official site (https://trac.transmissionbt.com/wiki/NAS) they are saying this:
transmission-daemon needs to be run with EVENT_NOEPOLL defined on the environment. This applies to all versions of libevent, up to the current (2.0.11-stable). Reason: epoll has bugs on the kernel shipped with these devices.
Example: EVENT_NOEPOLL=1 transmission-daemon -f
incorporated into the start-up script (needs to be adapted to the specific script used)
Problem: I have no idea what this means (what is epoll, what does it do, and how do I pass this command ?)
can anyone enlight me ?
Offline
mitorrents wrote:
mfpockets wrote:
augusto wrote:
Hi everyone.
I started using transmissions a few weeks ago and I've noticed that seeding works fine when I start (or restart) transmissions, but after a few hours it just stops seeding. For example I've downloaded Centos 5.6, and it should have completed a 1.5 ratio in a couple of days, but it has been running for a couple of weeks and it's not near that ratio. I should say too that I'm using v2.31.
On the other hand, if I seed that from my main computer using uTorrent, it starts seeding at full speed in no time.
Has anyone experienced the same problem? I remember reading a post in which someone mentioned that he restarted transmissions ever 12 hours... so I wonder if this is somehow related. Or do I need to tweak the config?
Thanks!Anyone else experiencing this? I just tried this out and it works great but after 30 mins to an hour I notice that all activity stops. If a add a file to download it will work, but previously seeding torrents just say seeding but never any activity. Stoping Transmission and then starting again seems to make the seeding kick in, even if only 5 or 10 kb (private torrent lots of seeds)
Having this issue as well. Just noticed it. I always thought that there were no more leechers and I would remove it from my queue. I tried with a file that had 200+ leechers and after the download completed it seeded for about 5 minutes max before stopping.
I'm afraid this is the wrong place to report this. Please go directly to the Transmission devs at www.transmissionbt.com (there's a forum and a bug tracker), so this can be dealt with.
Offline
StealthOne wrote:
Follow up... Looking on the Transmission forums and there appears to be others having this issue so it appears to be in the Transmission code.
https://forum.transmissionbt.com/viewto … mp;t=11649
KyleK... does this have anything to do with this bug: https://trac.transmissionbt.com/ticket/4260 ???
No, µTP should work fine with the release I put out, as I fixed this bug in my code already.
Offline
Just a thought, but did you guys try disabling µTP and see if the seeding behavior is still as bad?
$ transmission-remote --no-utp
Offline
KyleK wrote:
Just a thought, but did you guys try disabling µTP and see if the seeding behavior is still as bad?
Code:
$ transmission-remote --no-utp
I haven't tried that yet. It's worth a go, but from what other people are saying on the transmission support forum, it sounds like it's more to do with how peers are handled on private trackers. https://forum.transmissionbt.com/viewto … 762#p54969
Offline
Transmission2.32 is out and about!
The package is available from the usual location, please check it out.
(The seeding problems you were talking about are supposedly fixed, and I see quite an improvement in seeding here).
Offline
Hi KyleK,
Before updating, everything was running fine from 1.9. After updated to 2.31, the transmission-daemon keep crashing. Sometimes it can download for ten mins or even one hr, den it dies off.
Just updated to 2.32, same things happened. Currently, just can't start the daemon at all.
Any advice to troubleshoot it?
Thanks in advance
Offline
Try starting with a fresh configuration file and no inprogress torrents.
Offline
http://94.75.216.85/en/file/317843/Tran … 1-tgz.html
for people that can not download,
thx for the update
Offline
FunFiler wrote:
Try starting with a fresh configuration file and no inprogress torrents.
ok how do I resinstall? I'm using xp, can I just delete the transmission file away and reinstall?
Offline
I just noticed that the block list http://download.m0k.org/transmission/files/level1.gz is missing. Did something happen to it?
Offline
when i do
su nobody -c "transmission-daemon -f -g /i-data/2542aae3/transmission/.transmission-daemon -w /i-data/2542aae3/transmission -t -u username -v p0assowrd -a 127.0.0.1,192.168.*.*"
nothing happens
i ahd to replace the folder path because i am on a nsa110
Offline
Hello Kylek,
I've reported problems with transmission hanging-up earlier. Unfortunately I wasn't able to follow the discussion and do all the tests you asked... but after some manipulations transmission started working again!
a/ the problem is not about your version (I decided to upgrade to your version precisely because I started having this problem)
b/ basically, I let things dead for a couple of weeks... re-installed everything... then a clean start and re-uploaded torrents again...
I've had the thing working for 2 days now without those mysterious hangs, so I suppose as you suggested, that some torrents went bad and crashed the whole thing!
Offline
Hi Kylek,
Just updated to 2.32 as well ... the upgrade process seemed to go well.
When I type in the command # su nobady... etc as per the instructions I get the error message:
transmission-daemon: can't resolve symbol 'arc4random'.
When I go to clutch from the web browser an error comes up saying "It appears the daemon is not running".
Any ideas? Am using dns 323 with funplug .5
Cheers
Chumby
Offline
dez wrote:
FunFiler wrote:
Try starting with a fresh configuration file and no inprogress torrents.
ok how do I resinstall? I'm using xp, can I just delete the transmission file away and reinstall?
Best is to rename the folder /mnt/HD_a2/.transmission-daemon to something else (or moving it to a backup folder), and then use the instructions from the first post of this thread to set up Transmission as if you would do it for the first time.
Offline
lamski wrote:
I just noticed that the block list http://download.m0k.org/transmission/files/level1.gz is missing. Did something happen to it?
I have it somewhere deep in my head that the Transmission guys stopped providing a blocklist, but for the life of me I can't find any proof for that.
I believe there are other places which produce a compatible blocklist on a regular basis.
Offline
wiiguy1 wrote:
when i do
su nobody -c "transmission-daemon -f -g /i-data/2542aae3/transmission/.transmission-daemon -w /i-data/2542aae3/transmission -t -u username -v p0assowrd -a 127.0.0.1,192.168.*.*"
nothing happens
i ahd to replace the folder path because i am on a nsa110
Nothing as in no output on the screen?
Did you make sure you specified the '-f' parameter to run Transmission in the foreground?
You can check with 'top' or 'ps' if transmission-daemon is running in background.
Offline
Chumby wrote:
Hi Kylek,
Just updated to 2.32 as well ... the upgrade process seemed to go well.
When I type in the command # su nobady... etc as per the instructions I get the error message:
transmission-daemon: can't resolve symbol 'arc4random'.
When I go to clutch from the web browser an error comes up saying "It appears the daemon is not running".
Any ideas? Am using dns 323 with funplug .5
Cheers
Chumby
arc4random is a system call, that means it should be available for every program. This message tells me that something is weirdly wrong with your system.
Did you make sure uClibc is up-to-date on your system?
Offline
Thanks KyleK,
Just upgraded uCLIBC and the error disappears and I can run the #su nobody... command. Transmission seems to be looking at ports etc. I exit out however, but clutch is still saying daemon doesn't appear to be running.... any ideas from here? When I stop or start transmission in putty it seems to start/stop very quickly... makes me wonder if anything is happening at all...
Appreciate the help,
Cheers
Chumby
Offline
When you start Transmission using the '-f' parameter, it will run in foreground mode, that means as soon as you press Ctrl-C, or close PuTTY, Transmission will quit as well.
Running Transmission in foreground mode is only necessary once when you set it up for the first time (as described in the first post).
After that, you should use the startup script (/ffp/start/transmission.sh) to start and stop Transmission. You won't see anything on the screen when you use the script, but Transmission will run in the background.
So, the procedure is as follows:
1. Install/update Transmission
2. Set it up if you install for the first time:
$ su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /your/download/path -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*"
(Make sure the IP mask in the last parameter matches your local network).
You will see some output and if it doesn't show any error messages, press Ctrl-C to quit Transmission.
3. Now start Transmission in background mode (as a daemon):
$ /ffp/start/transmission.sh start
The web interface should work now.
Last edited by KyleK (2011-07-04 13:45:57)
Offline
Hi KyleK,
Yes thanks for that... have followed the above and it all seems to go to plan... the only thing different is that I have "/ #" prompt instead of the "$" prompt. Does that matter?
After starting it this way... I go back to clutch and it still says it doesnt appear to be working...
Any other ideas?
Cheers
Chumby
Offline