Sonarr random crashing as of recent - Ubuntu 16.04

Help & Support
#1

Sonarr version (exact version): 2.0.0.4326
Mono version (if Sonarr is not running on Windows): 4.6.1
OS: Xubuntu 16.04
((Debug logs)): https://drive.google.com/drive/folders/0B0P1BQaPpBrKWUJ2SFF0MmNrZzA?usp=sharing
Description of issue:

Been running sonarr on Xubuntu16.04 machine for about 7 or 8 months with no issues. Sometime recently, maybe in the last 3 weeks, I have noticed that sonarr would crash randomly, sometimes multiple times daily sometimes once a day. I am no expert on linux so maybe I am missing something and the logs will show. The other odd thing is that when it does crash it drives the CPU usage up to around 100% or close to it and runs forever, which then sends cpu temp through the roof. It seems like it will just run until something fails…I have never let it get to that but I have come home to find server cpu temp at 170 degree F. Usually if I am trans-coding something or anything to put stress on the CPU it will get up to 130 degrees max. Every time it shows mono/NzbDrone as using almost 100% of the cpu resources but its sonarr itself is not even running or accessible as it has crashed. So for fear of doing some damage I no longer run sonarr on boot or if I am not around.

Any thoughts or ideas? Maybe something to look at? Also, I have not made any changes to the system recently either except for some upgrades…mono being one of them recently.

#2

Did you recently upgrade mono? Mono 4.6 is new and aligns with your timeline. We’d need to see logs from when Sonarr has crashed, looking in the latest debug log file didn’t indicate any issues.

#3

Yeah, mono was upgraded around that time so that would make sense. Have there been any others with crashing issues with 4.6? I guess I could go back and install an older version. Is there a stable version that would be good to test on?

Ok, here are all the logs for NzbDrone. It did it today sometime while I was out, I was gone from 4 PM to 11 PM. Came home to sonarr not accessible and mono running using a ton of CPU and system running really hot. Hopefully this will show something. Let me know if I missed anything or if you need any other info.

Logs:

https://drive.google.com/open?id=0B0rIgA4g6rX4NlFucnlVbXRrcWs

#4

Some related to libgdiplus, but that case is very clearly logged, I’m not seeing anything related to that in the latest log.

4.2 would be best, 4.4 had issues with networking.

#5

Ok, I switched it to 4.2 and let you guys know if I still have that problem. Thanks.

1 Like
#6

I just found this post while trying to figure out a similar issue. My log were showing this when it died:

|Debug|GlobalExceptionHandlers|Minor Fail: The type initializer for 'System.Drawing.GDIPlus' threw an exception.

Looks like any time it tried to resize a poster it choked this way.

I was somehow missing libgdiplus.so.0 and installing it has fixed the problem entirely. I don’t know how this was working before or if my last update (which coincides with the start of the issues) caused it, but I can confirm that I am running mono 4.6 at this point. Perhaps that was updated?

In any case, “yum install libgdiplus-2.10-1.el6.x86_64” did the trick for CentOS 6.

1 Like
#7

Thanks I will see if I have that installed already, I downgraded to 4.2 mono and havent had a crash in over 24 hrs which is the longest its gone.

#8

I have had the same issue and found by default I was running mono 2.1 so i upgraded mono following

http://www.mono-project.com/docs/getting-started/install/linux/#usage

now it is stable

#9

I was running 4.6. I reverted back to 4.2 and I haven’t had a crash sense…so it seems it was mono causing the issue.

#10

after looking into this issue I have a fix for ubuntu /debian users

firstly upgrade to mono 4.6 http://www.mono-project.com/docs/getting-started/install/linux/#usage

then download and install the libmedia files https://mediaarea.net/en/MediaInfo/Download/Ubuntu

reboot and since then i have not had a single crash even with over 500tv shows and 35Tb of data

#11

Thanks Christopher. I reverted back to 4.2 or whatever it was recommended and ran that for a couple weeks and it ran perfect and I believe since then it’s updated to the current version of mono and I yet to have any problems since then so I think it was just something to do with that particular version or something was resolved either way it’s running perfect now. Thanks again.

#12

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