Troubleshooting Misc - Revision history

Bakerboy448: /* Wrong show type */

2021-05-06T21:54:55Z

Wrong show type

Bakerboy448: /* Sonarr */

2021-04-21T14:30:24Z

Sonarr

Bakerboy448: /* Wrong show type */ update per Markus (https://discord.com/channels/383686866005917708/383687854057979906/824297297620893696)

2021-03-24T16:04:53Z

Wrong show type: update per Markus (https://discord.com/channels/383686866005917708/383687854057979906/824297297620893696)

Bakerboy448: add examples to series type

2021-03-09T15:55:42Z

add examples to series type

Bakerboy448 at 20:52, 27 February 2021

2021-02-27T20:52:14Z

Bakerboy448 at 20:20, 27 February 2021

2021-02-27T20:20:47Z

Bakerboy448: /* Trace Logs Example */

2021-02-27T20:20:16Z

Trace Logs Example

Bakerboy448 at 20:19, 27 February 2021

2021-02-27T20:19:43Z

Drazzilb: /* Trace Logs Example */

2020-11-25T22:16:24Z

Trace Logs Example

Drazzilb: /* Trace Logs Example */

2020-11-25T22:15:25Z

Trace Logs Example

@@ Line 110: / Line 110: @@
 === Sonarr ===
 <section begin=sonarr_indexers_and_trackers_type />
-==== Wrong show type ====
+==== Wrong Show Type or Unknown Series ====
 The show type is another cause of poor search results. Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.

@@ Line 17: / Line 17: @@
 Just like the indexer/tracker test above, when you trigger a search while at Debug or Trace level logging, you can get the URL used from the log files. While testing, it is best to use as narrow a search as possible. A manual search is good because it is specific ''and'' you can see the results in the UI while examining the logs.
-In this test, you’ll be looking for obvious errors and running some simple tests. You can see the search used the url <code>https://api.nzbgeek.info/api?t=tvsearch&amp;cat=5030,5040,5045,5080&amp;extended=1&amp;apikey=(removed)&amp;offset=0&amp;limit=100&amp;tvdbid=354629&amp;season=1&amp;ep=1</code>, which you can try yourself in a browser after replacing <code>(removed)</code> with your apikey for that indexer. Does it work? Do you see the expected results? In that URL, you can see that it set specific categories with <code>cat=5030,5040,5045,5080</code>, so if you’re not seeing expected results, this is one likely reason. You can also see that it searched by tvdbid with <code>tvdbid=354629</code>, so if the episode isn’t properly categorized on the indexer, it will need to be fixed. You can also see that it searches by ''specific'' season and episode with <code>season=1</code> and <code>ep=1</code>, so if ''that'' isn’t correct on the indexer, you won’t see those results. Look at Manual Search XML Output below to see an example of a working query’s output.
+In this test, you’ll be looking for obvious errors and running some simple tests. You can see the search used the url <code>https://api.nzbgeek.info/api?t=tvsearch&amp;cat=5030,5040,5045,5080&amp;extended=1&amp;apikey=(removed)&amp;offset=0&amp;limit=100&amp;tvdbid=354629&amp;season=1&amp;ep=1</code>, which you can try yourself in a browser after replacing <code>(removed)</code> with your apikey for that indexer. Does it work? Do you see the expected results? [[Sonarr_FAQ#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|Does this FAQ entry apply?]] In that URL, you can see that it set specific categories with <code>cat=5030,5040,5045,5080</code>, so if you’re not seeing expected results, this is one likely reason. You can also see that it searched by tvdbid with <code>tvdbid=354629</code>, so if the episode isn’t properly categorized on the indexer, it will need to be fixed. You can also see that it searches by ''specific'' season and episode with <code>season=1</code> and <code>ep=1</code>, so if ''that'' isn’t correct on the indexer, you won’t see those results. Look at Manual Search XML Output below to see an example of a working query’s output.
 {{#spoiler:show=Manual Episode XML Output|hide=Click here to Close|
 <pre>

← Older revision		Revision as of 16:04, 24 March 2021
Line 113:		Line 113:

	The show type is another cause of poor search results. Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.		The show type is another cause of poor search results. Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.
		+
		+	Please note that if the series type is set to anime and none of your enabled indexers have any anime categories configured then it effectively skips the indexer and may appear that it is not searching.

	===== Show Type Examples =====		===== Show Type Examples =====

@@ Line 96: / Line 96: @@
 === Lidarr ===
 <section begin=lidarr_indexers_and_trackers_testing_a_search />
-Needs Testing a Search Write up for Lidarr
+Coming Soon(tm)
 <section end=lidarr_indexers_and_trackers_testing_a_search />
 === Readarr ===
 <section begin=readarr_indexers_and_trackers_testing_a_search />
-Needs Testing a Search Write up for Readarr
+Coming Soon(tm)
 <section ned=readarr_indexers_and_trackers_testing_a_search />
@@ Line 113: / Line 113: @@
 The show type is another cause of poor search results. Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.
 <section end=sonarr_indexers_and_trackers_type />

@@ Line 6: / Line 6: @@
 Just like the indexer/tracker test above, when you trigger a search while at Debug or Trace level logging, you can get the URL used from the log files. While testing, it is best to use as narrow a search as possible. A manual search is good because it is specific ''and'' you can see the results in the UI while examining the logs.
-In this test, you’ll be looking for obvious errors and running some simple tests. You can see the search used the url <code>LINK NEEDED</code>, which you can try yourself in a browser after replacing <code>(removed)</code> with your apikey for that indexer. Does it work? Do you see the expected results? In that URL, you can see that it set specific categories with <code>UPDATE CAT</code>, so if you’re not seeing expected results, this is one likely reason. You can also see that it searched by tmdb with <code>UPDATE TMDB</code>, so if the movie isn’t properly categorized on the indexer, it will need to be fixed. Look at Manual Search XML Output below to see an example of a working query’s output.
+In this test, you’ll be looking for obvious errors and running some simple tests. You can see the search used the url <code>"https://api.nzbgeek.info/api?t=movie&cat=2000&apikey=(removed)&q=O+Brother+Where+Art+Thou</code>, which you can try yourself in a browser after replacing <code>(removed)</code> with your apikey for that indexer. Does it work? Do you see the expected results? In that URL, you can see that it set specific categories with <code>2000</code>, so if you’re not seeing expected results, this is one likely reason. If the movie isn’t properly categorized on the indexer, it will need to be fixed. Look at Manual Search XML Output below to see an example of a working query’s output.
-{{#spoiler:show=Manual Episode XML Output|hide=Click here to Close|
+{{#spoiler:show=Manual Search XML Output|hide=Click here to Close|
 <pre>
-<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:newznab="http://www.newznab.com/DTD/2010/feeds/attributes/" version="2.0">
+coming soon
 </pre>
 <section end=radarr_indexers_and_trackers_testing_a_search />
@@ Line 196: / Line 126: @@
 ==== Code Block 1 ====
 <section begin=radarr_indexers_and_trackers_code_block />
-Radarr Code block 1
+Need to add logs of feed downloaded and parsed (rss)
 <section end=radarr_indexers_and_trackers_code_block />
 ==== Code Block 2 ====
 <section begin=radarr_indexers_and_trackers_code_block2 />
-Radarr Code Block 2
+Need to add logs of feed downloaded and parsed (search)
 <section end=radarr_indexers_and_trackers_code_block2 />
@@ Line 232: / Line 162: @@
 ==== Code Block 1 ====
 <section begin=lidarr_indexers_and_trackers_code_block />
-Lidarr Code Block 1
+Need to add logs of feed downloaded and parsed (rss)
 <section end=lidarr_indexers_and_trackers_code_block />
 ==== Code Block 2 ====
 <section begin=lidarr_indexers_and_trackers_code_block2 />
-Lidarr Code Block 2
+Need to add logs of feed downloaded and parsed (search)
 <section end=lidarr_indexers_and_trackers_code_block2 />
 === Readarr ===
 ==== Code Block 1 ====
 <section begin=readarr_indexers_and_trackers_code_block />
-Readarr Code Block 1
+Need to add logs of feed downloaded and parsed (rss)
 <section end=readarr_indexers_and_trackers_code_block />
 ==== Code Block 2 ====
 <section begin=readarr_indexers_and_trackers_code_block2 />
-Readarr Code Block 2
+Need to add logs of feed downloaded and parsed (search)
 <section end=readarr_indexers_and_trackers_code_block2 />

@@ Line 251: / Line 251: @@
 ==== Radarr ====
 <section begin=radarr_trace_logs_example />
-{{#spoiler:show=Manual Episode Search Trace Log|hide=Click here to Close|
+{{#spoiler:show=Manual Search Trace Log|hide=Click here to Close|
 <pre>Needs Trace Log Example</pre>}}
 <section end=radarr_trace_logs_example />
 ==== Sonarr ====
 <section begin=sonarr_trace_logs_example />
-{{#spoiler:show=Manual Episode Search Trace Log|hide=Click here to Close|
+{{#spoiler:show=Manual Search Trace Log|hide=Click here to Close|
 <pre>
 -11-20 13:15:23.6|Trace|Http|Req: 66 [GET] /api/v3/release?episodeId=1                                                                                                                                                                                                                         [5/3289]
@@ Line 340: / Line 340: @@
 ==== Lidarr ====
 <section begin=lidarr_trace_logs_example />
-{{#spoiler:show=Manual Episode Search Trace Log|hide=Click here to Close|
+{{#spoiler:show=Manual Search Trace Log|hide=Click here to Close|
 <pre>Needs Trace Log Example</pre>}}
 <section end=lidarr_trace_logs_example />
 ==== Readarr ====
 <section begin=readarr_trace_logs_example />
-{{#spoiler:show=Manual Episode Search Trace Log|hide=Click here to Close|
+{{#spoiler:show=Manual Search Trace Log|hide=Click here to Close|
 <pre>Needs Trace Log Example</pre>}}
 <section end=readarr_trace_logs_example />

@@ Line 4: / Line 4: @@
 === Radarr ===
 <section begin=radarr_indexers_and_trackers_testing_a_search />
-Needs Testing a Search Write up for Radarr
+Just like the indexer/tracker test above, when you trigger a search while at Debug or Trace level logging, you can get the URL used from the log files. While testing, it is best to use as narrow a search as possible. A manual search is good because it is specific ''and'' you can see the results in the UI while examining the logs.
 <section end=radarr_indexers_and_trackers_testing_a_search />
@@ Line 11: / Line 87: @@
 Just like the indexer/tracker test above, when you trigger a search while at Debug or Trace level logging, you can get the URL used from the log files. While testing, it is best to use as narrow a search as possible. A manual search is good because it is specific ''and'' you can see the results in the UI while examining the logs.
-In this test, you’ll be looking for obvious errors and running some simple tests. You can see the search used the url <code>https://api.nzbgeek.info/api?t=tvsearch&amp;cat=5030,5040,5045,5080&amp;extended=1&amp;apikey=(removed)&amp;offset=0&amp;limit=100&amp;tvdbid=354629&amp;season=1&amp;ep=1</code>, which you can try yourself in a browser after replacing <code>(removed)</code> w/ your apikey for that indexer. Does it work? Do you see the expected results? In that URL, you can see that it set specific categories with <code>cat=5030,5040,5045,5080</code>, so if you’re not seeing expected results, this is one likely reason. You can also see that it searched by tvdbid w/ <code>tvdbid=354629</code>, so if the episode isn’t properly categorized on the indexer, it will need to be fixed. You can also see that it searches by ''specific'' season and episode with <code>season=1</code> and <code>ep=1</code>, so if ''that'' isn’t correct on the indexer, you won’t see those results. Look at Manual Episode Search XML Output below to see an example of a working query’s output.
+In this test, you’ll be looking for obvious errors and running some simple tests. You can see the search used the url <code>https://api.nzbgeek.info/api?t=tvsearch&amp;cat=5030,5040,5045,5080&amp;extended=1&amp;apikey=(removed)&amp;offset=0&amp;limit=100&amp;tvdbid=354629&amp;season=1&amp;ep=1</code>, which you can try yourself in a browser after replacing <code>(removed)</code> with your apikey for that indexer. Does it work? Do you see the expected results? In that URL, you can see that it set specific categories with <code>cat=5030,5040,5045,5080</code>, so if you’re not seeing expected results, this is one likely reason. You can also see that it searched by tvdbid with <code>tvdbid=354629</code>, so if the episode isn’t properly categorized on the indexer, it will need to be fixed. You can also see that it searches by ''specific'' season and episode with <code>season=1</code> and <code>ep=1</code>, so if ''that'' isn’t correct on the indexer, you won’t see those results. Look at Manual Episode Search XML Output below to see an example of a working query’s output.
 {{#spoiler:show=Manual Episode XML Output|hide=Click here to Close|
 <pre>