Sonnar not grabbing new episodes

I’m running Sonarr on a Win7, using sabNZBd to download files. The setup works perfectly fine, however, recently I have not been able to download any episodes. When I go to NZBGeek or OZNzb, the files are listed for download but my Sonnar is not automatically grabbing them all, not even 12+ hours later.

Thanks and hope you can help
DKing

Are there any errors in the logs?
If you do a manual search in Sonarr for those episodes are there any rejections?
Are the series and episode both monitored?

There is no error except for

CommandExecutorUnknown error in thread: The operation was canceled.

And yes both series and episodes are both monitored. I went home from university the other day and my HDD wasn’t plugged in so I ran the computer and it kept erroring saying it couldn’t find the drive which makes sense. Sonnarr was automatically downloading the episodes but couldn’t process them and when I came back, I plugged the HDD and it auto processed them fine. But now it doesn’t get any episodes at all even though the indexers are all available.

We’ll need to see debug logs of an RSS sync while the release is on the RSS feed still to diagnose further.

It comes with a huge error now.

The RSS sync happened before debug logging was enabled. Best to hastebin the logs as well to avoid a super long thread.

http://hastebin.com/calosorogo.1c

I tried it again but I’m not sure if this is what you want.

7 posts were split to a new topic: AHD and TTN rss feed not working anymore

So tymanthiuis hijacked my thread, but does anyone have a solution to my issue?

Thanks

There you go, dehijacked :smile:

@markus101 can you look into it? I briefly scanned the log, but I don’t have much time.
One thing I noticed was the abundance of DownloadedEpisodesImportService, not sure if DF is on, but wouldn’t cause it not to grab anything. Otherwise it’s a download stuck in the queue trying to import over and over again.

@dorianking Which series are we talking about, and can you find such episode in the log file you posted?

It is all series, none of them are downloading, I would have to manually download them from NZBGeek or OZNzb

And how could we possibly know which series you watch and which episodes you already have. :smiley:

We need one episode that is still in the rss and you can grab manually. that way you can look in the log to see whether sonarr is seeing that release and why it’s rejecting it.

An example would be Last Man Standing. 5x07.

Its on NZBgeek but it doesn’t download into my SABnzbd. What should I do next?

you should check the sonarr log rss parsing, like you posted before, see if it’s listed there.

as example I’ll pick 5x05:
http://hastebin.com/calosorogo.1c
line 1899 till 1921, Sonarr is parsing the episode, rejecting it because the quality is wanted and the existing file is already at cutoff.

So you should check the log file the same kind of entry but then for 5x07. if it isn’t in there, then likely the episode is too old already to be in the last 100 items in the rss feed, in that case you’ll have to pick a more recent example, or go back to older log files.

Edit: please note that i’m actually away on holiday, and I can’t investigate in great detail from a hotel room wifi.

So if you said that it’s parsing the episode but rejecting it cause of the file size? I changed it all to unlimited and I still have the problem. But it’s now downloading episodes of much older episodes of other series and none of the new stuff.

I gave you an EXAMPLE of what to look for in the log. And I never mentioned size limits.

Ah I see

I found it.
http://hastebin.com/eqefusajoq.vhdl

15-11-6 20:47:14.3|Debug|AcceptableSizeSpecification|Item: Last.Man.Standing.US.S05E07.HDTV.x264-KILLERS, meets size constraints.
15-11-6 20:47:14.2|Debug|AcceptableSizeSpecification|Item: Last.Man.Standing.US.S05E07.720p.HDTV.x264-KILLERS, Size: 594717817 is greater than maximum allowed size (0), rejecting.

Can you show post a screenshot of your Quality size settings?

Set it to something slightly less than unlimited (as temporary workaround) seems to be a bug with the null check.

@markus101 can you repro and fix that? My guess it’s stored as 0 in the db, instead of null.