Transmission

Thanks mate, I'll go ahead and file a ticket, I just wanted to make sure I was not goofing something in the handmade RPC call before I did that.

Have you tried transmission-remote -i torrent_hash?

-i --info id | torrent-hash
Show details of the current torrent(s)

http://linux.die.net/man/1/transmission-remote

Perhaps I am missing something, but without the "-t" option you will only get an error "No torrent specified! Please use the -t ...

Well that did not take long :D

Here is an example of what I see using the transmission-remote (cli version) application. [transmission-remote -t HASH_HERE -i]

This is a torrent where the tracker has thrown the unregistered torrent error and has a backup tracker; You can see that there is not a ...

Here's some slightly out-of-date, but still enlightening, info.
https://forum.transmissionbt.com/viewtopic.php?f=1&t=6684


Thanks for the link, indeed a good read, too bad the multitracker-spec.txt file is not readily available on the bittornado site ( http://archive.today/KXDbA ). By reading ...

"Tracker will be used as a backup"
Isn't this only used when both trackers are the same, but one is udp and one is http? If that is the case, then the error likely would apply to both. Normally, I only see one tracker per tier.

I don't think this is the case, the torrents in question have ...

Well it looks like the backup tracker is simply never consulted, since the initial tracker did indeed respond with an error. I say this as a torrent that hits this issue will have both trackers listed in the trackers section with backup tracker only showing "Tracker will be used as a backup" while ...

I have recently run into an issue with how transmission reports errors, in most cases when a tracker returns an error it transmission puts it in the error property field. Unfortunately this does not happen if there is a backup tracker and the error reported by the primary one is not a communications ...

I can not wait for 2.83 so I can implement this verification post download. I find Transmission to be a great client, but get burned from time to time by corrupted downloads.

Cheers guys!

I am experiencing an odd issue when trying to verify torrents after they download with the 2.82 (14160) build. I have a script set to run when a torrent completes, and part of that script is to tell the daemon to verify said torrent when it completes. I have implemented this via the script-torrent ...