Menu

#4 not updating ratios

Arctic
open
nobody
5
2013-02-03
2005-03-22
r00ted
No

Another user, Ningen, at the methlabs.org Arctic thread.

But, basically, I use the demonoid site/tracker, and it's
not updating my ratio like it's supposed to. I posted to
there forum, and someone replied stating:

[quote]As I understand it, the tracker does't "ask" for
anything regarding the ratio. It uses "event=stopped"
sent from your client to the tracker. Thats as much as I
know about it as Im not a coder.[/quote]
though, the replied user wasn't a mod/admin. But I have
heard something similar from other threads there (not
about arctic in particular), that it relies on the client to
send the ul info when the transfer stops/ed.

Overall the client is working good, Im seeding many files:
http://img187.exs.cx/img187/2181/arctic4zq.png but the
tracker isn't updating my stats.

I've seen many posts of users saying to "Pause" the
download to update the info, well, I tried that (by
manually pausing each and every torrent, then
Resuming it 1 minute after, and also tried using
the "Pause All" and "Resume All" option from teh tray
menu. I also tried using the force re-announce by right
clicking every single torrent. I went through and did a
force reannounce on each of the torrents.

So, Im not sure, maybe Arctic isn't sending the
event=stopped message? Also, would it be piossible to
send the ul/dl stats more often? Incase of a spuradic
reboot (my stepdad rebooting:P).

Discussion

  • r00ted

    r00ted - 2005-03-28

    Logged In: YES
    user_id=770894

    here's what demonoid has to say:

    ===========start quote============
    The Demonoid tracker uses the event=stopped message
    (which is part of the BT protocol) to update the ratios.

    You won't get credit if any of the following happen;
    * Your computer crashes or the power fails.
    * You close the client and physically turn off the machine too
    soon before the all-important event=stopped message is sent
    (some clients take longer than others and especially if you're
    seeding multiple torrents. If you want to shut down in a hurry
    be sure that your client has completely finished doing it's job
    by confirming all application (client) activity in the Task
    Manager has ceased.
    * Your client is a pile of manure and doesn't follow BT
    protocol and send the message to the tracker. Such clients
    are (but not limited to) TorrentStorm, BitTorrent++,
    NovaTorrent, BitComet*, BitSpirit... *Versions v0.49 and up
    support
    * The tracker is temporarily down.
    * The packet did not get through due to the unforseen nature
    of the internet. Unfortunately not every single piece of data
    gets to it's destination - and even then not always error free.
    Your client often rejects packets of corrupted data of the file
    you're downloading sent by other peers.

    If you don't have a fixed IP it could also happen because;
    * Your ISP disconnects you periodically (some ISPs do this).
    * You are momentarily disconnected.
    * You close the client properly and reboot...
    ...AND...(with all of the above) you fail to log on to the site to
    tell it - the tracker - your new IP after reconnecting and/or
    rebooting.
    What happens is when you get disconnected your IP
    changes and the tracker assigns the data credit to the last
    known IP. Of course you don't have this IP anymore so if you
    fail to inform it of your new IP (you inform it by logging
    on/visiting the site after you are back online) then you'll lose
    the credit.

    Additionally, if the tracker has a heavy load, the internet is
    slow or Deimos is tweaking the code then you will
    experience a delay for your ratio to be updated or not get the
    credit if the event=stopped fails to get through for these
    reasons.

    And in extremely rare circumstances data can be lost due to
    a HD failure, RAM overload (when the peer count is too high),
    site hosting problem or when we are under a DDoS attack.
    There was an occasion where we lost forum threads and
    some member account data due to above reasons.

    IMPORTANT NOTE: Emphasizing and reiterating the above,
    the event=stopped message gets sent, on either STOPPING
    YOUR TORRENTS, PAUSING YOUR TORRENTS (if the
    client supports it) or CLOSING YOUR CLIENT. This is what
    everyone who uses Demonoid MUST understand. It is up to
    the user to use a recommended client in the above manner to
    ensure their ratios are updated and calculated correctly.

    Edit: Please note that The ratio is updated 24 hours after the
    transfer stops as noted on the top of every page (under your
    username & stats).

    FAQs;

    1. "What can I do to ensure that I don't lose credit in the
    case of something happening that is out of my control, like a
    power cut or I get disconnected?'
    To prevent accidental or unfortunate loss of upload credit due
    to some of the unforseen events described above you should
    regularly pause/stop/close your torrents/clients so the
    tracker updates your ratio. Every 4 - 8 hours is
    recommended. It's good BT practice.
    =========end quote=============

    so basically, would it be possible to have a "frequency" that
    arctic would send the ul/dl info to the tracker? Or issue the
    force re-announce, so users dont loose there credit? :P
    Especially living in FL, we get power outtages alot. Though, I
    cant say that's the cause of my recent ratio/credit losses.
    So something to have arctic send the info every 10 minutes,
    would be awesome. So I dont loose that much data transfer
    credit.

    And, I dont know if it's possible, but on exit/shutdown, to
    have it force re-announce the torrents/tracker? If not, some
    periodic force reannounce would suffice I think :P

     
  • Teloriun

    Teloriun - 2005-05-24

    Logged In: YES
    user_id=879686

    All though not a fix, try doing a forced announce before you
    pause the torrent. I find that this suvvessfully updates the
    tracker with the amounts youve upped 'n down'd.

    XBT had the same issue until the author added an
    optional "send stop" statement upon pausing a torrent or
    closing the client.

     

Log in to post a comment.