I’m using NZBGet 16.0 with sonarr master 2.0.0.3357. This always worked fine but since a couple of weeks the failed downloads are not handled correctly sometimes.
In nzbget the download failed with status: DELETE: SCAN
This is because of the following log:
INFO Wed Oct 14 2015 08:40:58 Collection ** added to history
ERROR Wed Oct 14 2015 08:40:58 Error parsing nzb-file **.nzb
ERROR Wed Oct 14 2015 08:40:58 Error parsing nzb-file: Start tag expected, ‘<’ not found
In sonarr the download is stuck in activity with timeleft: 00:00:00 and progress empty. However an episode is downloaded correctly and added through sonarr(I guess this is another download or something but I can’t verify this as completed downloads gets deleted from the nzbget log. But in Sonarr the completed episode is added on 8:41 so I guess it’s another one.)
Beside this I also configured sonarr to remove failed downloads from nzbget but this particular download isn’t removed from the nzbget log also. Looks like it’s not detected correctly or something.
Got 2 broken downloads this morning again seems sonarr crashes:
Logs shows:
15-10-16 08:41:44.2|Info|Nzbget|Adding report [The Player 2015 S01E04 720p HDTV x264-FLEET] to the queue.
15-10-16 08:41:44.4|Trace|CommandExecutor|CheckForFinishedDownloadCommand → DownloadMonitoringService
15-10-16 08:41:44.4|Trace|CommandQueueManager|Marking command as started: CheckForFinishedDownload
15-10-16 08:41:44.6|Debug|NzbgetProxy|Url: http://localhost:6789/jsonrpc
15-10-16 08:41:44.6|Debug|NzbgetProxy|Url: http://localhost:6789/jsonrpc
15-10-16 08:41:44.6|Trace|NzbgetProxy|Response: {
15-10-16 08:41:45.2|Trace|ConfigService|Using default config value for ‘downloadclienthistorylimit’ defaultValue:‘30’
15-10-16 08:41:45.2|Warn|ProcessDownloadDecisions|Couldn’t add report to download queue. The Player 2015 S01E04 720p HDTV x264-FLEET
NzbDrone.Core.Download.Clients.DownloadClientException: Failed to add nzb The Player 2015 S01E04 720p HDTV x264-FLEET.nzb
at NzbDrone.Core.Download.Clients.Nzbget.Nzbget.AddFromNzbFile (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode, System.String filename, System.Byte fileContent) [0x00000] in :0
at NzbDrone.Core.Download.UsenetClientBase1[NzbDrone.Core.Download.Clients.Nzbget.NzbgetSettings].Download (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Download.DownloadService.DownloadReport (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Download.ProcessDownloadDecisions.ProcessDecisions (System.Collections.Generic.List1 decisions) [0x00000] in :0
I removed a part of the json response, as this didn’t include any information about the show. But I can send you more logs if needed.
I’m not really sure if it’s the same release(but I think so) but somehow it seems to work when I manually retry it(a few hours later, the broken nzb was retrieved just after startup of sonarr in the morning(nas starts up at 8:30). Somehow sonarr can’t fetch a correct nzb or something.
nzbget log for the download:
Fri Oct 16 08:41:44 2015 INFO Adding collection The Player 2015 S01E04 720p HDTV x264-FLEET.nzb to queue
Fri Oct 16 08:41:44 2015 ERROR Error parsing nzb-file: Start tag expected, ‘<’ not found
Fri Oct 16 08:41:44 2015 ERROR Error parsing nzb-file The Player 2015 S01E04 720p HDTV x264-FLEET.nzb
Fri Oct 16 08:41:44 2015 ERROR Could not add collection The Player 2015 S01E04 720p HDTV x264-FLEET.nzb to queue
Fri Oct 16 08:41:44 2015 INFO Collection The Player 2015 S01E04 720p HDTV x264-FLEET added to history
mono needs to be runnign with the --debug switch and currently isn’t.
This looks like the release failed to get sent to nzbget (invalid NZB), knowing where the NZB came from (which indexers do you have enabled), coupled with logs should help track down the problem.
nzbget erroring on some nzb files Sonarr passes it (ie. doesn’t like the nzb file itself and therefore fails during parsing it and doesn’t attempt to process it further).
Sonarr doesn’t seem to (fully) recognise this as a failed download (technical a not-even-started-downloaded, but the same result) and it hangs around in the Sonarr activity window instructing the user to take a look in the downloader client (as I presume it would with say a password-protected downloaded that required end-user interaction).
Guess this is a change that occurred with nzbget v16 (and onwards) as it is around about here I started seeing this issue.