Sonarr Crash after about 2 minutes

Help & Support
1

I updated my Sonarr to latest version, im using mono and Ubuntu 14.

Trace logs

http://pastebin.com/fM6QXr2z

2

Exactly which version of Sonarr and mono?

How did you upgrade Sonarr?
Was anything else updated recently? (maybe mediainfo?)

3 
http://pastebin.com/s1PHUtF8

I upgraded using apt-get

4

I am having the same issue except in my case it is a fresh install and i assumed i did something wrong. Sonarr just dies with no error in its logs etc. It could happen in 2 minutes for up to 24 hours later for me but never lasts more than 24 hours. Only difference is i am on mediainfo v0.7.67 but i an now updating to see if it helps. Ubuntu 14.10.

There has been a few things i have noticed.

  1. I noticed in upstart logs that sometimes mono itself is crashing. I have other mono apps and they are fine so assume it is something Sonarr is hitting but not sure what. I have not been seeing that in the logs for a few days or i would post it.
  2. The higher the logging level the faster it dies. (changed to trace logging to try to get more info and now sonarr lasts a lot less than 24 hours)
  3. I get a lot of errors about files already exist when copying large file to very slow storage. Only thing i can think of here is that maybe because the copy is taking 2-4 minutes that the copy process is somehow being triggered multiple times for the same file since it runs every minute i think. The drive it is copying to is a fuse drive but nothing else seems to have an issue with it as far as i can tell.

If someone thinks it may be mono is there a better version to use?

5

Been dealing with this as well over the past day. Crashing restarting etc.

Was really thinking my might miss some of these problems but fell into this hole :smile:

Sonarr v 2.0.0.3037
Mono 3.12.1 tarball Fri mar 6 2015 (been ok up this this)
ubuntu 14.04.1 server 64 bit (in a KVM) 4 GB mem

And a couple of hours work of logs to sort thru…

I also notice I’m not able to finish a library update without it restarting…

http://pastebin.com/D2xPRLYR
http://pastebin.com/gCLU0sQd
http://pastebin.com/Hc59MFuv
http://pastebin.com/UaYuJuBk
http://pastebin.com/zQPj5DSX
http://pastebin.com/BzjSG2L5
http://pastebin.com/9uccbhG7
http://pastebin.com/mXeNu9VL
http://pastebin.com/EXib4TDN
http://pastebin.com/FG5E33XM

This was at trace level, lot of data here. Hope it helps. I think you might even find an Epic Fail in here as well that is also spoke about in another thread.

Package list if it will help or accurate enough

http://pastebin.com/QhYitFSb

Edit, just in, I just came home to sonarr running twice… checking with htop

debug restarts it right? Have to watch for this when things start to sour

6

Any idea what issue could be?

7

Good news and less good news.

Good news:

  • We’re able to reproduce these issues in a live environment
  • We have some more information as to whats causing them

Less good news:

We don’t have a solution for these crashes, at the moment there are multiple different causes, so we’re trying to focus on the more common ones, but they all appear to be related to slightly different things and not directly in Sonarr’s code, but something we’re doing which causes a lower level failure (in mono).

We’ll be putting together another thread as there are currently numerous threads on the same issue and its not feasible to track them all. The thread will be stickied at the top, so keep an eye out for that.

8

Thanks for the feedback

9

I have now switched to a windows host and everything is working fine. Seems like it was all mono issues sadly

10

Thank you letting us know! :slight_smile:

11

Would disabling “Analyse video files” remove the mediainfo influence?

12

MediaInfo is still used to detect sample files, so it is still used regardless of that setting. Runtime is the most reliable way to detect if its a sample or not.