Sonarr not downloading better quality episodes (cutoff unmet)

Help & Support
1

Hello,

New user here, migrated from SB after 2 years, running NZBdrone/sonarr torrents branch inside Docker container, configured according to wiki (Completed download handling).

I’m loving the program so far, great UI from usability and aesthetics perspective. The only issue I have is that sonarr is not automatically downloading better quality episodes, even though they show up as wanted (cutoff unmet) and they are always found when the automatic search is manually activated from the wanted window.

For some reason it ignores better qualities unless it is manually told to download them. Is there a setting somewhere that I’m missing? In this regard, Sickbeard was always looking for better versions and downloading them automatically.

Your help is highly appreciated!

2

Sonarr doesn’t run searches on a schedule, it just watches RSS feeds from your indexers for Neely posted content to see if its wanted. https://github.com/NzbDrone/NzbDrone/wiki/FAQ#how-does-nzbdrone-find-episodes

3

Nevertheless, shouldn’t it be able to find the better quality episodes in the rss? It hasn’t found a single one…
I will try with a higher frequency interval to see if it catches them. I’m not sure this is the problem because then I would also have missing episodes and so far it hasn’t missed a single one.

4

Have they been posted recently?
Are the episodes listed on the Cutoff not met page? (are they monitored)?

Whats your RSS interval? 15 minutes is plenty, even at peak times things don’t fall off the latest 100 that fast.

5

The episodes are listed on the ‘cutoff unmet’ section. I will try with 30 minutes interval to see if it helps.

6

Well I can now confirm that it didn’t help, i.e. it hasn’t downloaded the better quality even though it appeared on the rss. Looking at the log I now see some strange error messages, all exactly the same:

/opt/NzbDrone/Microsoft.AspNet.SignalR.Core.dll Error : 0 : SignalR exception thrown by Task: System.AggregateException: One or more errors occured ---> System.IO.IOException: Write failure ---> System.Net.Sockets.SocketException: The socket has been shut down
  at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x00000] in <filename unknown>:0 
  at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in <filename unknown>:0 
  at System.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0 
  at System.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0 
  at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
 --> (Inner exception 0) System.IO.IOException: Write failure ---> System.Net.Sockets.SocketException: The socket has been shut down
  at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x00000] in <filename unknown>:0 
  at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in <filename unknown>:0 
  at System.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0 
  at System.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0 
  at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0

Any ideas where to look are hugely appreciated.

7

We’ll need to see some debug logs while the release is on the RSS feed. With mono running with the --debug switch.

That error can be ignored, its not critical and has nothing to do with your issue (its a library we use for UI messages that doesn’t like it when the browser session is closed).

8

Ok, I will try to do it. That’s not as easy as it sounds, because atm nzbdrone is running inside a docker container…