[Mldonkey-bugs] [bugs #10073] bittorrent event=completed more than once, messing up tracker stats

[anonymous]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a multi-networks file-sharing client.

/**************************************************************************/
[bugs #10073] Latest Modifications:

Changes by: Anonymous user
Date:  
                Mon 01/03/2005 at 08:32

------------------ Additional Follow-up Comments ----------------------------
thanks,

I can see people already using MLdonkey/2.5-28h and no
duplicated event=completed is sent. No one has connected 
with 2.6.29 yet, but I have good hope that it is fixed now (:

cu,
maurice






/**************************************************************************/
[bugs #10073] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=10073>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: Fri 08/20/2004 at 14:38

Category:  Bittorrent-Plugin
Severity:  5 - Average
Item Group:  Program malfunction
Resolution:  Fixed
Privacy:  Public
Assigned to:  None
Status:  Open
Release:  2-5-27
Release:  2.5-12 to 2.5-27
Platform Version:  None
Binaries Origin:  CVS / Self compiled
CPU type:  None


Summary:  bittorrent event=completed more than once, messing up tracker stats

Original Submission:  Hi,

I have just notice on my tracker that MLdonkey sends
event=completed more than once and thereby messes up
the tracker stats totaly. In numbers:
(log from 19/Aug/2004:06:26:07 to 20/Aug/2004:16:16:57)

    196 MLdonkey 2.5-12
     70 MLdonkey 2.5-16r
     57 MLdonkey 2.5-21g
      8 MLdonkey 2.5-27
     40 MLdonkey 2.5-27b
total: 371

these where all from only 8 different IPs

see http://bitconjurer.org/BitTorrent/protocol.html for reference..

cu
Maurice Massar
massar(at)unix-ag.uni-kl.de
PS: there are in fact reports for which "Binaries Origin:"
just does not make any sense... (I don't run mldonkey at all)


Follow-up Comments
------------------


-------------------------------------------------------
Date: Mon 01/03/2005 at 08:32       By: 0 <None>
thanks,

I can see people already using MLdonkey/2.5-28h and no
duplicated event=completed is sent. No one has connected 
with 2.6.29 yet, but I have good hope that it is fixed now (:

cu,
maurice

-------------------------------------------------------
Date: Mon 01/03/2005 at 08:14       By: Amorphous <amorphous>
no they should send UserAgent MLdonkey/2.5-28h . i'm sure i fixed this... just 
checked 2.6.29 has the fix, too

-------------------------------------------------------
Date: Mon 11/01/2004 at 18:05       By: 0 <None>
# fgrep event=completed /var/log/apache2/access.log | sed -re 's/([^ ]* 
){,11}//' | sort | uniq -c | fgrep MLdonkey
     13 "MLdonkey 2.5-16q"
     98 "MLdonkey 2.5-16r"
    119 "MLdonkey 2.5-16t"
     14 "MLdonkey 2.5-21c"
    113 "MLdonkey/2.5-28"

does not look any better now..
it seems like one MLdonkey/2.5-28 sends
19 event=completed in this timeframe,
one exactly every 30 minutes.

I have not seen a UserAgent MLdonkey/2.5-28h,
or do all -28 send just MLdonkey/2.5-28?

-------------------------------------------------------
Date: Mon 11/01/2004 at 17:30       By: spiralvoice <spiralvoice>
Does the problem still happen with newer MLDonkey versions?
Especially with 2-5-28h where some BT improvements took place?




CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
massar --AT-- unix-ag --DOT-- uni-kl --DOT-- de | 









For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=10073>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/