RTorrent Magnet not resolved

[gpapaz]

I try to access an rtorrent client on a seedbox over httprpc. I use the rarbg indexer, which correctly identifies episodes for my series. They use magnet files which rtorrent should be able to handle. I also have kat indexer which uses torrent files and they work as expected - found, added, started etc. But for the rarbg magnets I get the following debug logs:

15-12-19 00:56:47.4|Debug|RTorrentProxy|Executing remote method: load.normal 15-12-19 00:56:47.8|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:48.7|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:49.7|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:50.6|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:51.5|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:52.4|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:53.3|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:54.5|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:55.4|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:56.3|Debug|RTorrentProxy|Executing remote method: d.name 15-12-19 00:56:57.2|Debug|RTorrent|Could not find hash 170C0FE522035F0F43543AC97872CAF3D9DE5681 in 10 tries at 500 ms intervals. 15-12-19 00:56:57.2|Debug|RTorrent|rTorrent could not resolve magnet magnet:?xt=urn:btih:170c0fe522035f0f43543ac97872caf3d9de5681&dn=Into.the.Badlands.S01E04.Two.Tigers.Subdue.Dragon.1080p.WEB-DL.DD5.1.H264-NTb%5Brartv%5D&tr=http%3A%2F%2Ftracker.trackerfix.com%3A80%2Fannounce&tr=udp%3A%2F%2F9.rarbg.me%3A2710&tr=udp%3A%2F%2F9.rarbg.to%3A2710&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce. Removing

And of course it is never added in the rtorrent client. The funny thing is that when I copy pasted the magnet part in the rtorrent web ui, it was correctly added. Any ideas what is happening here?

Looking around source codes from Sonarr and httprpc plugin , I found that the later doesn’t include a d.name method. Only a d.get_name is specified. Could that be the issue sonarr fails to retrieve the name associated with the hash?

[markus101]

d.name replaced d.get_name in newer rTorrent versions, I believe it took effect in 0.9.

[gpapaz]

OK, interesting! I asked my seedbox provider to give me info regarding their rtorrent installation. I am waiting for their reponse. The ruttorrent and httprpc installations are of version 3.6, one before the latest. What is also interesting is that the link I posted, is for the latest httprpc plugin code and there, they only support the d.get_name command. Am I wrong? Does this mean they also need to update their code? Is there a way for Sonarr to determine the version of rtorrent client and use the correct method name? Or is my only way to use magnet files with rtorrent to utilize a blackhole?

[markus101]

The original author stated he tested it with a couple different plugins:

rTorrent support

I’ve tested rtorrent using the rpc and the httprpc plugins in ruTorrent and both have worked for me. Sonarr successfully added a torrent and imported it after completion, using each plugin. Note that you should only have one of these plugins installed at a time, never both. The host and port settings are for your web server that is hosting rutorrent. So if it’s on the same box as Sonarr, this will usually work (depending on your web server setup): localhost and port 80. The unique part for …

We don’t plan to support the old get_name to avoid complication and at the moment blackhole doesn’t support magnet links.

[gpapaz]

I spoke too soon … The correct method is used and not the old one. I am still checking the 3 projects’ source code to determine what is going wrong and magnet is not added from xmlrpc, but the same magent URI is correctly added by rutorrrent’s UI.

[gpapaz]

It looks like the issue was with the implementation of rTorrent xml-rpc communication in Sonarr, at least through the ruTorrent’s httprpc plugin. I have made a pull request, that fixes this. Let me know what you thing of it, thanks!