| Summary: | KTorrent doesn't seed as other clients do | ||
|---|---|---|---|
| Product: | [Applications] ktorrent | Reporter: | Francesco Frassinelli <fraph24> |
| Component: | general | Assignee: | Joris Guisson <joris.guisson> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | junk, lachs0r, mpartap |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
KTorrent log
KTorrent log 2 KTorrent log 3 |
||
|
Description
Francesco Frassinelli
2010-07-13 12:22:59 UTC
Version ? KTorrent 4.0.2, over KDE 4.4.92 (KDE 4.5 RC2) on a Fedora Rawhide (i686). It sounds to me that you are not getting any incoming connections. Can you post your log file of a situation like this ? The log file is ~/.kde/share/apps/ktorrent/log Created attachment 49145 [details]
KTorrent log
What I've done: 1. I deleted ~/.kde/share/apps/ktorrent/, so everything is clean 2. I've started KTorrent 3. I've created a new torrent 4. I've started (on the same host) aria2 5. Nothing happened 6. I've refreshed the tracker (now KTorrent can see the leecher) 7. Nothing happened 8. I've closed aria2 9. I've closed KTorrent Details: 1. 87.5.154.163 is my ip 2. http://tracker.openbittorrent.com/announce and udp://tracker.openbittorrent.com:80/announce are the tracker I used (I don't know why but KTorrent seems to give me always a timeout error on udp trackers) You are getting incoming connections looking at your log. I see attempts of ktorrent trying to connect to itself the first time (logical at that moment KT is the only peer), those connections are dropped. There are two incoming connections which are probably not from ktorrent. Authentication fails on both of them. Could be encryption settings. Can you check the encryption settings of aria2 ? I didn't specify any encryption setting on aria2. Man says:
--bt-min-crypto-level=plain|arc4
Set minimum level of encryption method. If several encryption methods are provided by a peer, aria2 chooses the lowest one which satisfies the given level. Default: plain
This is what happened:
1. aria2 tried to connect to KTorrent with the non-default ecryption method (--bt-min-crypto-level=arc4), but nothing happened, so I've quitted it
2. deluge trying to connecting to KTorrent: everything is ok, so I've interrupted the download and I've quitted it, in crypto-only mode
3. Transmission on another pc (it worked), in crypto-only mode
4. I've allowed KTorrent to use non-encrypted streams, and I've used aria2, with no successful
5. Another transmission client on another pc seems ok.
So... Seems that only aria2 gives problem with KTorrent, and sometimes Transmission needs some extra-time in order to start. It could be an aria2 bug.
On another pc I've KTorrent 4.0.1, over Fedora 13 x86_64 (stable, not rawhide). Same problem with Transmission. Initially, encryption was disabled on KTorrent, and allowed in Transmission, and nothing worked. Then, I've enabled KTorrent encryption, but the situation was the same. Both clients uses upnp. I've tried another time with aria2 (on the same pc), but it didn't work. I'll attach the log. Created attachment 49207 [details]
KTorrent log 2
Created attachment 49208 [details]
KTorrent log 3
Now, I've upgraded KTorrent on my laptop to version 4.0.2, and I'm downloading OpenSUSE 11.3 LiveCD KDE 4 i686. KTorrent upload rate is near 0. The log file is litterally full of message like: ven lug 16 14:42:01 2010: Authentication to [ip] : failure When I say "full", I mean that I've about 850 messages like this, from hundreds of different ip. Every minutes another ~100 of this messages appear. At this time, I'm over 1050 messages of this kind. Also there are this kind of messages: ven lug 16 14:45:23 2010: Error thrown: Illegal token: 65 ven lug 16 14:45:23 2010: Error happened during parsing : Illegal token: 65 [...] ven lug 16 14:45:23 2010: Timeout occurred The last one is not related with the tracker. What is the status of this bug ? I have no problems with downloading the opensuse live cd with encryption enabled. As for the autentication failure messages, that is pretty normal, seeing that most people run with encryption off. I can't provide you other information until the end of semptember, because I'm on holiday. I suggest you to try to create a new torrent and then download it with another client (I've not tested KTorrent - KTorrent download), because it didn't work for me (as you can see at the beginning of this bug report). I'll do more tests in order to verify if it depends on encryption, but I would like to remember that in my previous tests I've set KTorrent in order to allow non-encrypted communications. (still not seeding @r1169101) This was fixed in the 4.1 branch some time ago This bug has NOT been fixed as of KTorrent 4.3.1. Still seeing the same misbehavior on my machines. I have the same problem with v 4.3.1. I know I don't see all the seeds because I only see 1 peer, who receives the file from someone else. It happened 3 times recently, with different torrents. I solved the problem : uninstall KTorrent, install Transmission, use Transmission. Finally, I see all the available seeds. |