From 5734eb8d6c3d909e341215f8713d1c81835fde86 Mon Sep 17 00:00:00 2001 From: Donald Webster Date: Sat, 14 Dec 2019 20:39:45 -0800 Subject: [PATCH] Add testing a download section --- Downloads-and-Importing.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Downloads-and-Importing.md b/Downloads-and-Importing.md index 6cc54e8..22ee384 100644 --- a/Downloads-and-Importing.md +++ b/Downloads-and-Importing.md @@ -4,4 +4,7 @@ Downloading and importing is where *most* people experience issues. From a high Start by using the [[Logging and Log Files]] article to turn logging up to trace, it is likely you're going to need to look at them to figure out what is wrong. And if you can't, anyone you ask for help will need to see them for sure. Remember to get them from the actual log file, put them in a pastebin and show us context around what we need to see. Nobody wants to dig through the whole trace log (it is huge!), but just a line or two is unlikely to help. # Testing the Download Client -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. \ No newline at end of file +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. \ No newline at end of file