Sonarr not fetching Jeopardy episodes

I have Sonarr properly pointed to Jackett which points to IPT. This is tested working as it pulls most other shows, but it is not properly pulling Jeopardy. It appears that Sonarr looks for Jeopardy by year and episode number (e.g. 2019x110) while IPT and pretty much every other torrent site I’m finding have it listed by air date since there are so many episodes (e.g. 2019 06 05). I’m assuming this mismatch is why Sonarr is not pulling the episodes.

For reasons I don’t understand, Wheel of Fortune seems to be fine. Same mismatch exists though.

I mistakenly posted this to GitHub as a bug originally and got a response that I needed to set the Series type to “Daily” - I’ve done that, but still no luck. Not sure if I need to force a refresh or what, but it still won’t pull Jeopardy episodes from IPT.

Update: If I click on the episode title under the “Wanted” tab, go to the “Search” tab and hit “Automatic Search,” it works. It will pull a torrent and put it under “Activity” and pass it off to Transmission for download.

But if I click “Search All Missing” it runs through the list very quickly and comes back empty-handed.

Search all missing (and a season level search) uses season searches, which IIRC for daily is the year + month in a specific format. Jackett likely doesn’t understand that format and doesn’t pass a request to the indexer that it returns results for.

Debug logs will show the exact request Sonarr is making, Jackett may need to be updated to support that.

So I enabled debug logs and then did both - the “search all missing” as well as the specific episode -> “automatic search” force - and these are the logs that were produced showing the unsuccessful request for the first attempt, and the successful request for the second. I’m not really sure what I’m looking at here so maybe you can tell me what the difference in the requests is? Wouldn’t “search all missing” effectively just be making the same request the “automatic search” does, but just multiplied by how many things are in the Wanted queue?

19-6-5 19:20:47.9|Debug|Api|[PUT] /api/config/host: 202.Accepted (124 ms)
19-6-5 19:20:48.0|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:48.0|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:48.1|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:48.2|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:48.3|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:48.3|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:53.2|Debug|Api|[GET] /api/wanted/missing?page=1&pageSize=15&sortKey=airDateUtc&sortDir=desc&filterKey=monitored&filterValue=true: 200.OK (56 ms)
19-6-5 19:20:53.3|Debug|Api|[GET] /api/wanted/missing?page=1&pageSize=15&sortKey=airDateUtc&sortDir=desc&filterKey=monitored&filterValue=true: 200.OK (35 ms)
19-6-5 19:20:54.7|Debug|Api|[POST] /api/command: 201.Created (5 ms)
19-6-5 19:20:54.9|Info|EpisodeSearchService|Performing missing search for 108 episodes
19-6-5 19:20:55.0|Info|NzbSearchService|Searching 1 indexers for [Jeopardy! : 2019]
19-6-5 19:20:55.0|Debug|Torznab|Downloading Feed,5040&extended=1&apikey=(removed)&offset=0&limit=100&q=Jeopardy&season=2019
19-6-5 19:20:55.3|Debug|NzbSearchService|Total of 0 reports were found for [Jeopardy! : 2019] from 1 indexers
19-6-5 19:20:55.3|Debug|NzbSearchService|Setting last search time to: 6/5/2019 11:20:55 PM
19-6-5 19:20:55.4|Info|DownloadDecisionMaker|No results found
19-6-5 19:20:55.4|Info|EpisodeSearchService|Completed missing search for 108 episodes. 0 reports downloaded.
19-6-5 19:20:57.8|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:57.8|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:20:57.8|Debug|Api|[GET] /api/diskspace: 200.OK (86 ms)
19-6-5 19:20:57.9|Debug|Api|[GET] /api/diskspace: 200.OK (82 ms)
19-6-5 19:20:58.5|Debug|Api|[GET] /api/log?page=1&pageSize=50&sortKey=time&sortDir=desc: 200.OK (5 ms)
19-6-5 19:20:58.5|Debug|Api|[GET] /api/log?page=1&pageSize=50&sortKey=time&sortDir=desc: 200.OK (4 ms)
19-6-5 19:20:59.3|Debug|Api|[GET] /api/log/file: 200.OK (2 ms)
19-6-5 19:20:59.3|Debug|Api|[GET] /api/log/file/sonarr.debug.txt: 200.OK (1 ms)
19-6-5 19:21:00.5|Debug|Api|[GET] /api/log/file/sonarr.debug.txt: 200.OK (1 ms)
19-6-5 19:21:26.0|Debug|Api|[GET] /api/wanted/missing?page=1&pageSize=15&sortKey=airDateUtc&sortDir=desc&filterKey=monitored&filterValue=true: 200.OK (58 ms)
19-6-5 19:21:26.1|Debug|Api|[GET] /api/wanted/missing?page=1&pageSize=15&sortKey=airDateUtc&sortDir=desc&filterKey=monitored&filterValue=true: 200.OK (35 ms)
19-6-5 19:21:30.5|Debug|Api|[POST] /api/command: 201.Created (5 ms)
19-6-5 19:21:30.6|Info|NzbSearchService|Searching 1 indexers for [Jeopardy! : 2019-05-30]
19-6-5 19:21:30.6|Debug|Torznab|Downloading Feed,5040&extended=1&apikey=(removed)&offset=0&limit=100&q=Jeopardy&season=2019&ep=05/30
19-6-5 19:21:30.9|Debug|NzbSearchService|Total of 1 reports were found for [Jeopardy! : 2019-05-30] from 1 indexers
19-6-5 19:21:30.9|Debug|NzbSearchService|Setting last search time to: 6/5/2019 11:21:30 PM
19-6-5 19:21:30.9|Info|DownloadDecisionMaker|Processing 1 releases
19-6-5 19:21:30.9|Debug|DownloadDecisionMaker|Processing release 'Jeopardy 2019 05 30 720p HDTV x264-NTb' from 'IPT via Jackett'
19-6-5 19:21:30.9|Debug|Parser|Parsing string 'Jeopardy 2019 05 30 720p HDTV x264-NTb'
19-6-5 19:21:30.9|Debug|Parser|Episode Parsed. Jeopardy - 2019-05-30 
19-6-5 19:21:30.9|Debug|Parser|Language parsed: English
19-6-5 19:21:30.9|Debug|QualityParser|Trying to parse quality for Jeopardy 2019 05 30 720p HDTV x264-NTb
19-6-5 19:21:30.9|Debug|Parser|Quality parsed: HDTV-720p v1
19-6-5 19:21:30.9|Debug|Parser|Release Group parsed: NTb
19-6-5 19:21:30.9|Debug|AlreadyImportedSpecification|Performing alerady imported check on report
19-6-5 19:21:30.9|Debug|AlreadyImportedSpecification|Skipping already imported check for episode without file
19-6-5 19:21:30.9|Debug|AcceptableSizeSpecification|Beginning size check for: Jeopardy 2019 05 30 720p HDTV x264-NTb
19-6-5 19:21:30.9|Debug|AcceptableSizeSpecification|Item: Jeopardy 2019 05 30 720p HDTV x264-NTb, meets size constraints.
19-6-5 19:21:30.9|Debug|MaximumSizeSpecification|Maximum size is not set.
19-6-5 19:21:30.9|Debug|LanguageSpecification|Checking if report meets language requirements. English
19-6-5 19:21:30.9|Debug|ReleaseRestrictionsSpecification|Checking if release meets restrictions: Jeopardy 2019 05 30 720p HDTV x264-NTb
19-6-5 19:21:30.9|Debug|ReleaseRestrictionsSpecification|[Jeopardy 2019 05 30 720p HDTV x264-NTb] No restrictions apply, allowing
19-6-5 19:21:30.9|Debug|QualityAllowedByProfileSpecification|Checking if report meets quality requirements. HDTV-720p v1
19-6-5 19:21:30.9|Debug|MinimumAgeSpecification|Not checking minimum age requirement for non-usenet report
19-6-5 19:21:30.9|Debug|RetentionSpecification|Not checking retention requirement for non-usenet report
19-6-5 19:21:30.9|Debug|SeriesSpecification|Checking if series matches searched series
19-6-5 19:21:30.9|Debug|DelaySpecification|Ignoring delay for user invoked search
19-6-5 19:21:30.9|Debug|HistorySpecification|Skipping history check during search
19-6-5 19:21:30.9|Debug|MonitoredEpisodeSpecification|Skipping monitored check during search
19-6-5 19:21:30.9|Debug|DownloadDecisionMaker|Release accepted
19-6-5 19:21:32.9|Debug|Transmission|Downloading torrent for episode 'Jeopardy 2019 05 30 720p HDTV x264-NTb' finished (7600 bytes from
19-6-5 19:21:32.9|Info|DownloadService|Report sent to Transmission. Jeopardy 2019 05 30 720p HDTV x264-NTb
19-6-5 19:21:32.9|Info|EpisodeSearchService|Episode search completed. 1 reports downloaded.
19-6-5 19:21:37.9|Debug|Parser|Parsing string 'Jeopardy.2019.05.30.720p.HDTV.x264-NTb'
19-6-5 19:21:37.9|Debug|Parser|Episode Parsed. Jeopardy - 2019-05-30 
19-6-5 19:21:37.9|Debug|Parser|Language parsed: English
19-6-5 19:21:37.9|Debug|QualityParser|Trying to parse quality for Jeopardy.2019.05.30.720p.HDTV.x264-NTb
19-6-5 19:21:37.9|Debug|Parser|Quality parsed: HDTV-720p v1
19-6-5 19:21:37.9|Debug|Parser|Release Group parsed: NTb
19-6-5 19:21:37.9|Debug|TrackedDownloadService|Tracking 'Transmission:Jeopardy.2019.05.30.720p.HDTV.x264-NTb': ClientState=Downloading (readonly) SonarrStage=Downloading Episode='Jeopardy - 2019-05-30 HDTV-720p v1' OutputPath=/media/tv/Jeopardy.2019.05.30.720p.HDTV.x264-NTb.
19-6-5 19:21:38.0|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (2 ms)
19-6-5 19:21:38.0|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (2 ms)
19-6-5 19:21:51.0|Debug|Api|[GET] /api/wanted/missing?page=1&pageSize=15&sortKey=airDateUtc&sortDir=desc&filterKey=monitored&filterValue=true: 200.OK (73 ms)
19-6-5 19:21:51.1|Debug|Api|[GET] /api/wanted/missing?page=1&pageSize=15&sortKey=airDateUtc&sortDir=desc&filterKey=monitored&filterValue=true: 200.OK (42 ms)
19-6-5 19:21:52.7|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:21:52.8|Debug|Api|[GET] /api/health: 200.OK (1 ms)
19-6-5 19:21:52.8|Debug|Api|[GET] /api/diskspace: 200.OK (106 ms)
19-6-5 19:21:53.0|Debug|Api|[GET] /api/diskspace: 200.OK (104 ms)
19-6-5 19:21:54.0|Debug|Api|[GET] /api/log?page=1&pageSize=50&sortKey=time&sortDir=desc: 200.OK (5 ms)
19-6-5 19:21:54.1|Debug|Api|[GET] /api/log?page=1&pageSize=50&sortKey=time&sortDir=desc: 200.OK (4 ms)
19-6-5 19:21:54.9|Debug|Api|[GET] /api/log/file: 200.OK (2 ms)
19-6-5 19:21:54.9|Debug|Api|[GET] /api/log/file/sonarr.debug.txt: 200.OK (1 ms)
19-6-5 19:21:55.9|Debug|Api|[GET] /api/log/file/sonarr.txt: 200.OK (2 ms)

No, it groups by season to reduce the number of API calls it makes.

No month, but the year. Which probably results in Jackett making a request for Jeopardy S2019 as the tracker itself doesn’t have indexing to support Jeopardy + 2019.

Okay, so that makes sense, but now it’s been 24 hours and a new episode of Jeopardy just streeted. Sonarr knew about it, because it came up in the Wanted list with an Air date of 12 hours ago (today it says “Yesterday”). But it still failed to queue anything up for download until I click the specific episode and do the “automatic search” again. So it’s not really performing in the automated capacity I am hoping for.

Is whatever cron that runs to get new missing items just doing the same API call that “search all missing” does, thus not giving Jackett anything to work with? Is there a way to fix this? Clear out the older episodes or something so that it will feel more comfortable only asking for one thing at a time?

No, it doesn’t search, as explained in the FAQ.

You’re going to need to look at debug logs to see if Sonarr ever sees the release on the RSS feed and why it rejected it. Make sure debug logging is enabled and check the logs after the next release comes out.

I still have debug mode on, and did skim the logs before posting… didn’t see Jeopardy even mentioned except for where I forced the automatic search. So perhaps I’m not understanding then… is Sonarr only capable of finding things automatically that are advertised on the RSS feed, but can use Jackett to run an active search against the tracker’s entire database?

Could this mean that even though the tracker carries the latest Jeopardy episodes, they just don’t advertise them on their RSS?

That is how Sonarr finds new releases, it only searches automatically to find a replacement for a failed download.

It can do that for any indexer that supports searching, including Jackett.

RSS is the latest releases, I’ve never known an indexer to not include specific releases. Beyond that it could be too long of an RSS Sync interval (the default of 15 should be fine), using Jackett’s aggregate indexer (/all instead of each indexer individually in Sonarr meaning you can get more gaps in the RSS Sync/less search results as Sonarr will usually avoid paging).

Jackett should only be contacting one tracker, IPT, since that’s all I have configured. Not sure if /all would still limit the results of the only tracker it contacts. The only reason I use Jackett is because it appears Sonarr was not able to integrate with IPT, because even using it’s RSS, it wasn’t getting anything, even stuff that I knew was being advertised on the RSS. I was told on other forums that Jackett was a requirement to properly use private trackers like IPT, so that’s really all it’s doing. It logs into IPT on my behalf and presents a Torznab feed for Sonarr’s use.

Right, I know how Jackett operates. You can use IPT directly with Sonarr, but that only works for RSS, not searching (since they have an RSS feed, but don’t have an API).

If the debug logs don’t show Jeopardy before you went and searched it then Sonarr had no opportunity to grab it, also look for Indexer "indexer name" rss sync didn't cover the period between X and Y UTC. Search may be required. that is Sonarr complaining that the RSS feed from the indexer got more items than Sonarr could request (as well as more than it could page back to request), which is max 1000 (10 pages of 100 items), but could be 100 if IPT doesn’t allow paging, in which case you’d want to shorten the RSS Sync interval.

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