Mirrors/Sonarr
1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr.git synced 2024-11-21 18:22:42 +01:00
Code Issues Releases Wiki Activity

Add testing an import section.

Donald Webster 2019-12-14 20:45:58 -08:00
parent 5734eb8d6c
commit df31da4f20
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Downloads-and-Importing.md

@ -7,4 +7,9 @@ Start by using the [[Logging and Log Files]] article to turn logging up to trace
Start by testing the download client, if it doesn't work you'll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you've gotten the username, password or apikey wrong.
# Testing a Download
Now we'll try a download, pick a show and do a manual episode search. Pick one of those episodes and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it end up in the trace level logs during the **Check For Finished Download** task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since Sonarr searches by **tvdbid** most of the time, it can queue up an episode with a name that it can't recognize.
Now we'll try a download, pick a show and do a manual episode search. Pick one of those episodes and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it end up in the trace level logs during the **Check For Finished Download** task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since Sonarr searches by **tvdbid** most of the time, it can queue up an episode with a name that it can't recognize.
# Testing an Import
Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they're not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are *permissions* issues, remember that Sonarr needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.
Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that Sonarr gets the path to the download *from* the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don't have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.