Hi,

Thought i drop a quick question here before i go to sleep..

How does the latest svn behave regarding the reports of downloaded/uploaded data? Does it update the upload/download stats for every byte that's downloaded or per 'block' or chunk?

Issue that i'm having is that the tracker is trying to keep track of the speed ppl are uploading to try and keep the cheating a bit lower, but this seems to be causing some issues from time to time that causes the tracker to think that i have been uploading in X MB/s.. Have not found any bugreports that talk about this (except for that old one that should have been fixed..)

Interface stats and ktorrent upload seems to be a match so i think the issue is in how the data is reported and not that it's sending to much uploaded.

If you have ANY ideas, or just want to brainstorm with me about it, of what might be causing this and maybe an answer for the above question and i'll have a happier but very tired head...

follow-up question...

When a torrent has finished downloading and it does the stopped/started events, are those multi-threaded so on a loaded system or a bad connection to the tracker could result in that the started event gets posted to the tracker before the stopped event?

When a torrent is finished, we only send a completed event there is no start and stop involved.

What is the announce interval of this tracker ?

KTorrent only starts a bunch of KIO jobs, so it doesn't really have control over the order these jobs are executed. This can be added, but unless the announce interval is very short, I don't see much reason to.

30 minutes... but it does seem to send a stop/start.. heres a shortened debuglog for one torrent during it's 'completion-pass' + request before and after.

# cat ktorrent-debug-20070627-2.log |grep tracker |grep "493568980"
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... 7%2f%2b%8e
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... 7%2f%2b%8e
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... 7%2f%2b%8e
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... 7%2f%2b%8e
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... 7%2f%2b%8e


So the torrent does seem to get stopped and started at completion..

How much time is between those loggings ?

basicly almost none.... but it depends on how loaded the machine is...

whenever a torrent is completed you get something like this.. lines are cut here, but all the tracker requests here are for the same torrent.

Chunk 0 downloaded
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... pleted&in$
Moving data for torrent Datasakerhet to /storage/Ktorrent/downloads/
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... ed&info_h$
Saving 0 chunk downloads
Saving list of peers to /storage/Ktorrent/downloads_inprogress/tor35/peer_list
Authentication to 85.227.164.123 : failure
Starting download
Loading list of peers from /storage/Ktorrent/downloads_inprogress/tor35/peer_list (num_peers = 9)
Doing tracker request to url : http://tracker:80/announce.php?passkey= ... ed&info_h$
Data directory changed for torrent 'Datasakerhet' to: /storage/Ktorrent/downloads/
Doing scrape request to url : http://tracker:80/scrape.php?passkey=76 ... b%a2%23%7d
Scrape : leechers = 0, seeders = 16

You are moving the files when the download is completed. Because of this the torrent has to be stopped temporarely.

So this is normal and values passed to the tracker seem to be OK
Maybe there is an issue with the order these announces reach the tracker.

I'm gonna make sure they are executed in the correct order.

Thanks for the assistance.

Just drop a post if it will be in the svn or in a patch.


.

I just want to confirm that something is wrong. Recently I got banned on one of the trackers, because some weird data kTorrent had sent - based on that, tracker counted that my upload is like 500MB/s (or sth) which is of course not true. Admins thought I was cheating. Fairly enough, they accepted my explanation and unbanned me, but for now (until it get's fixed) I have to use another client for this tracker. Or will turning off moving data after completion (I use that feature) help in the mean time?

This is fixed in the current SVN version. I fixed it yesterday.

Thanks... I'll drop a note after i have stress-tested it and give you a preliminary report how it works.