EPIC FAIL Message, Sonarr Randomly Crashes

Help & Support
1

Sonarr: 2.0.0.3953
Mono: 4.2.1 (Stable 4.2.1.102/6dd2d0d Thu Nov 12 09:52:44 UTC 2015)
OS: Ubuntu Server 14.04.4 LTS Kernel 4.2.0-27-generic

Debug logs: http://hastebin.com/uwisowoxem.avrasm

Description of issue:
Sonarr seems to randomly crash. I stood a new Ubuntu server, installed Sab and Sonarr. Sonarr started crashing and since it was a new install I just started over to see if that resolved my issue. Sonnar continues to crash at random times. I start it using “sudo service nzbdrone start” command. The only messages I see in the logs that might be related are what I’ve linked to using hastebin.

EPIC FAIL: Object reference not set to an instance of an object: Object reference not set to an instance of an object

System.NullReferenceException: Object reference not set to an instance of an object
  at System.Threading.Timer+Scheduler.ShrinkIfNeeded (System.Collections.Generic.List`1 list, Int32 initial) <0x7fdce2a50800 + 0x00022> in <filename unknown>:0 
  at System.Threading.Timer+Scheduler.SchedulerThread () <0x7fdce2a4ff40 + 0x0060d> in <filename unknown>:0 
  at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) <0x7fdce28b1010 + 0x00099> in <filename unknown>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x7fdce28af850 + 0x0016e> in <filename unknown>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x7fdce28af820 + 0x00020> in <filename unknown>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) <0x7fdce28af770 + 0x00059> in <filename unknown>:0 
  at System.Threading.ThreadHelper.ThreadStart () <0x7fdce28b11d0 + 0x0002e> in <filename unknown>:0
2

Looks like the same issue that popped up in the 4.1 kernel:

Unfortunately the issue exists somewhere between the kernel and mono and Sonarr is taken down when mono crashes.

3

I’m also seeing this behavior. Random crashes in 30s-30min intervals.

Mono version: 4.2.1
mediainfo version: v0.7.67

EPIC FAIL: Object reference not set to an instance of an object: Object reference not set to an instance of an object

System.NullReferenceException: Object reference not set to an instance of an object
at System.Threading.Timer+Scheduler.ShrinkIfNeeded (System.Collections.Generic.List`1 list, Int32 initial) <0x7f74b3650800 + 0x00022> in :0
at System.Threading.Timer+Scheduler.SchedulerThread () <0x7f74b364ff40 + 0x0060d> in :0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) <0x7f74b34b1010 + 0x00099> in :0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x7f74b34af850 + 0x0016e> in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x7f74b34af820 + 0x00020> in :0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) <0x7f74b34af770 + 0x00059> in :0

4

The issue lies with mono and the kernel or in some cases physical memory issues (memtest for 12+ hours would confirm that).

5

Thanks - I’ll run a memtest this evening, though I’ve seen it on two sets of ECC memory on the same machine, so I doubt that’s the cause. Is there a known-stable configuration of kernel/mono?

6

This (long) thread has information on when kernel fixes were available, but then in subsequent versions it was broken (linked in that thread and above in this thread).

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.