Debugging help: incorrect stats reported by private trackers

[djhomeless]

Hi All,
Could someone help me debug my transmission setup to help me track down a problem I am seeing on private trackers?

In a nutshell, I am seeing radically different stats wrt upload data from my local transmission client vs what the trackers are reporting that I have uploaded. Download speeds/reporting are fine, so just upload stats that are announced back.

I use a variety of private trackers and they all seem to be showing me as uploading only about 20% of what transmission says I have uploaded - this is not isolated on a particular torrent, so unfortunately I'm seeing this across the board. So before raising a bug on either side, I'd like to collect some data so not to waste anyone's time...

Some info about my setup:

Ubuntu 10.10
Transmission-daemon (2.13 - 11547)
Disabled PX and DHT
Ports opened and verified

I used to run rtorrent on this setup and never had the same problem, but I'm only marginally *nix intelligent so I don't rule out user error in my setup.

Thanks all,

Geoffrey

[Jordan]

If you run your transmission-daemon in the foreground with TR_CURL_VERBOSE set, it'll dump the tracker announces to the terminal:

Try something like this from bash:

Code: Select all

TR_CURL_VERBOSE=1 transmission-daemon -f 2>/tmp/announces.txt

...and the announces will be logged in /tmp/announces.txt." from there you can look at the uploaded= and downoaded= fields in the announce messages.

[rb07]

Have you taken into account that stats are only fully reported to the tracker when you pause a torrent?

It also happens if you delete a torrent, or it "finishes", or for all torrents when you stop Transmission. And reporting might fail, when the tracker doesn't respond, but Transmission should retry later.

[djhomeless]

Try something like this from bash:

Code: Select all

TR_CURL_VERBOSE=1 transmission-daemon -f 2>/tmp/announces.txt

I have a startup script for t.d. in /etc/init.d, could this command be merged there? I tried entering in the command from shell, but it just hung there (unless I'm intended to run it from screen?).

Have you taken into account that stats are only fully reported to the tracker when you pause a torrent?

It also happens if you delete a torrent, or it "finishes", or for all torrents when you stop Transmission. And reporting might fail, when the tracker doesn't respond, but Transmission should retry later.

Hmm, but my transmission setup is pretty 24/7, so since adding these torrents I haven't "paused" them. Still, if you're right maybe before I go too far down the rabbit hole I should try pausing the torrents and checking back in the morning to see if the stats on their side are updated (most of these trackers appear to update stats once a day...).

Thanks all...

[Jordan]

I have a startup script for t.d. in /etc/init.d, could this command be merged there? I tried entering in the command from shell, but it just hung there (unless I'm intended to run it from screen?).

Better to Keep It Simple and leave the startup script alone.

If by "just hung there" you mean it didn't show any output... the output was probably all going to /tmp/announces.txt...

[djhomeless]

If by "just hung there" you mean it didn't show any output... the output was probably all going to /tmp/announces.txt...

Indeed you were correct! Ok, I'll run this bad boy in screen then, thanks!