These instructions can be followed exactly if you are running qBittorrent in Docker, e.g. linuxserver/qbittorrent. If you aren't, you can figure it out.
- Download the linux_amd64 package from GitHub Releases.
- Extract the
ttbinary into whatever directory you volume mount as/config. - Create a config file
tt.tomlin that same directory with the contents:Change your username and password. Change[qbit] server = "http://localhost:8080" username = "admin" password = "password":8080if you changed theWEBUI_PORT. - Configure qBittorrent to run this program when a torrent is added. Under Tools >> Options, Downloads tab, set "Run external program on torrent added" to:
/config/tt qbit reannounce "%I"
- List torrents
tt [d|q] ls - Reannounce a torrent until it's healthy, via "Run external program on torrent added":
/config/tt qbit reannounce "%I" - Report stats in InfluxDB line protocol, for use as in the telegraf execute plugin:
[[inputs.exec]] commands = [ "/data/bin/tt deluge stats", "/data/bin/tt qbit stats", ]
I started tortle (tt) as a way to list the contents of Deluge and qBittorrent, and that became:
tt deluge ls --columns=ratio,name
tt qbit ls --columns=ratio,name
With that output you can do all sorts of things, like calculate the average ratio for torrents matching "sever":
./tt qbit ls --noheader --columns=ratio,name --filter=sever | column -s, -t | awk 'BEGIN { total=0; num=0; } { num++; total += $1; } END { print "num=" num; print "total=" total; print "avg=" (total/num); }'
Then I discovered that none of the qbit "reannounce scripts" worked like I thought they should, and that became:
tt qbit reannounce [hash]
Maybe there will be other subcommands in the future, maybe not.
Short answer: because the autobrr builtin reannounce feature breaks Skip Duplicates. I would have grabbed an existing script, but thier logic didn't agree with the gold standard HBD script1, and none of the ones I looked at 2,3,4,5 logged all the detail I needed to understand what was going on.
This implementation differs from and I think improves on the autobrr builtin reannounce in the following ways:
- It runs separate from the autobrr hook, so the hook is free to move on and write the release status so that Skip Duplicates has a better chance of working.
- It logs verbosely exactly what it is seeing and doing.
- It iterates 2 extra times like the deluge-reannounce script.
(3) seems the least well-reasoned, but this logic came from the HBD script for "racing using Deluge", it was duplicated in my Python fork, and it has never failed me.
Based on my experience with this script and instrumenting the deluge code, I now see that (3) is totally unnecessary, and yet I have not removed it. Libtorrent does not immediately announce when you call force_reannounce.
Footnotes
-
HBD script for "racing using Deluge". NB: Does not work with Deluge v2.1.1, so key-str0ke created a Python script with the same logic and I [forked it and added logging]https://github.com/kenstir/deluge-reannounce/). ↩
-
go-qbittorrent func
ReannounceTorrentWithRetry↩