Invalid torrent file specified error

Help & Support
1

Sonarr version (exact version): 2.0.0.5228
Mono version (if Sonarr is not running on Windows): n/a
OS: Windows 10 Pro
Debug logs:
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here. Post in .txt not .doc, .rtf or some other formatted document)
Description of issue:

I occasionally get the error below for episodes that Sonarr attempts to grab.

Message
Couldn't add report to download queue. * episode name*: Invalid torrent file specified

Exception
MonoTorrent.TorrentException: Invalid torrent file specified ---> MonoTorrent.BEncoding.BEncodingException: Illegal BEncodedDictionary. The attributes are not ordered correctly. Old key: announce-list, New key: announce
   at MonoTorrent.BEncoding.BEncodedDictionary.DecodeInternal(RawReader reader, Boolean strictDecoding) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\BEncoding\BEncodedDictionary.cs:line 85
   at MonoTorrent.BEncoding.BEncodedDictionary.DecodeInternal(RawReader reader) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\BEncoding\BEncodedDictionary.cs:line 67
   at MonoTorrent.BEncoding.BEncodedValue.Decode(RawReader reader) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\BEncoding\IBEncodedValue.cs:line 145
   at MonoTorrent.BEncoding.BEncodedValue.Decode(Stream stream) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\BEncoding\IBEncodedValue.cs:line 99
   at MonoTorrent.Torrent.Load(Stream stream, String path) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\Torrent.cs:line 701
   --- End of inner exception stack trace ---
   at MonoTorrent.Torrent.Load(Stream stream, String path) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\Torrent.cs:line 711
   at MonoTorrent.Torrent.Load(Byte[] data) in C:\BuildAgent\work\5d7581516c0ee5b3\src\MonoTorrent\Torrent.cs:line 556
   at NzbDrone.Core.MediaFiles.TorrentInfo.TorrentFileInfoReader.GetHashFromTorrentFile(Byte[] fileContents) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\MediaFiles\TorrentInfo\TorrentFileInfoReader.cs:line 14
   at NzbDrone.Core.Download.TorrentClientBase`1.DownloadFromWebUrl(RemoteEpisode remoteEpisode, String torrentUrl) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\TorrentClientBase.cs:line 188
   at NzbDrone.Core.Download.TorrentClientBase`1.Download(RemoteEpisode remoteEpisode) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\TorrentClientBase.cs:line 117
   at NzbDrone.Core.Download.DownloadService.DownloadReport(RemoteEpisode remoteEpisode) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\DownloadService.cs:line 76
   at NzbDrone.Core.Download.ProcessDownloadDecisions.ProcessDecisions(List`1 decisions) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\ProcessDownloadDecisions.cs:line 76

I didn’t get it as a debug log as it would be hard to capture but there still seems to be a lot of detail above.
Is it possible to understand from this what the issue is? The indexers that have the episode are reached via Jackett, which is installed on the same machine as Sonarr and the torrent client.

Also, as multiple indexers have this episode torrent, if one fails would it try a different indexer?

2

The torrent is in a format not supported by Sonarr, if you’re getting it often there may be an indexer that continues to use the unsupported format.

Try narrowing down which indexer is the culprit and disabling it in Sonarr.

Yes it will.

3

Thanks for your response. Is it possible to tell from the log file which indexer it was? Also, as multiple indexers had the same episode torrent it would mean all the indexers with the same torrent would have failed, which is odd as they are reliable indexers. Manually grabbing the failed torrent also worked.

4

Debug or trace logs should show the URL used to grab the torrent.

If multiple indexers had the exact same torrent they would fail, but they could also have a different torrent for the same episode and it wouldn’t fail.

The error is due to an old deprecate way of creating the torrent I believe, anything created in the new format wouldn’t have that issue.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.