Ubuntu 12.04 - NZBDrone Hard Locks

Hey All,

Whenever I do anything intensive in NZBDrone (eg - renaming a bunch of series, manually scanning for episodes, etc) the system hard locks until I kill the service. While my initial impression is that NZBD is a better product than SB… SB rarely if ever crashed. Any guidance that you can provide would be appreciated.

System =
Ubuntu 12.04 (LTS)
Mono 3.2.x

Output of error -->

/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.ObjectDisposedException: The object was used after being disposed.
at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x00000] in :0
at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0
— End of inner exception stack trace —
at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0
at System.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in :0
at System.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in :0
at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in :0
— End of inner exception stack trace —
–> (Inner exception 0) System.IO.IOException: Write failure —> System.ObjectDisposedException: The object was used after being disposed.
at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x00000] in :0
at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0
— End of inner exception stack trace —
at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x00000] in :0
at System.Net.ResponseStream.InternalWrite (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in :0
at System.Net.ResponseStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in :0
at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x00000] in :0

Thanks again.

~Spritz

I’m now also getting this error nearly everytime I do anything -->

app.js : 0
Uncaught TypeError: Cannot read property ‘_listenerId’ of undefined

Thanks.

The first error itself wouldn’t cause any crashing, when you say intensive, are you running multiple of these operations at the same time? We saw a lot of these issues with mono 2.10.x, but 3.2 has been much more stable.

The second error is purely UI, reloading the UI should take care of it.

I would have it searching for 3-4 episodes at a time, but not hundreds. At worse, I would expect a system slow down, not a crash. And to verify, this is the mono version -->

root@yakko:~# mono --version
Mono JIT compiler version 3.2.1 (Debian 3.2.1+dfsg-1~pre2)
Copyright © 2002-2012 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen

~Spritz