I’ve been using Sonarr for a while now and until January 19th it has worked with out any issues. My operating system is Ubuntu 14.04. Starting on the 19th Sonarr would stop working after only a few minutes. I think I was running mono version 3.12 at the time. Since then I’ve done a purge of the mono install and reinstalled. That helped a little as it now runs for a few days. I’ve also purged mono and Sonarr and removed the apt config for mono and Sonarr to start from scratch. I did that last Saturday and the system was running until today around 0556. After the last purge I’m now running Sonar 2.0.0.2850 and Mono 3.10.0. The normal nzbdrone.txt in UI (after restarting) doesn’t show anything useful. However the logs in /var/log/upstart/nzbdrone.log.1.gz are showing a segmentation fault when if finally dies and another error from /opt/NzbDrone/Microsoft.AspNet.SignalIR.Core.dll that happens well before the seg fault. Below is the latest copy of the upstart log just before the first error. Any suggestions?
edit: Can’t figure out how to use pastebin to embed the log, so here is a link to my log file.
The signalR can be ignored, it just logs that when it loses connection to the browser and its trying to send a new UI message (nothing to worry about).
For the seg fault, please enable trace logging so we can see which part of the RSS sync was running when the error occurred.
You’re not running mono 3.10 and Sonarr 2.0.0.2850?
Was this what was running when it crashed?
Also make sure mono is running with the --debug switch.
I’m using the upstart method to start Sonarr and have confirmed mono is running with the --debug switch. I’ve also enabled trace logging in Sonarr. I am running mono 3.10 and Sonarr 2.0.0.2850. I did have 3.12 in the past when this problem first started on 19 Jan. During my troubleshooting I completely removed Sonarr and mono, including removing the repositories. I did have another repository which was providing mono. After that I followed the ubuntu guide to setup Sonarr. Now all my system detects is mono 3.10. It is working with 3.10 for a few days. If you think I need to have mono 3.12 I will look into compiling it, but I’d like to wait a few days until it crashes before I do that.
3.10 has been a lot more reliable from what we’ve seen, its been working well for a few months whereas 3.12 has been out about a month and had issues from the get-go.
I thought I was going to have to a few days before it crashed again but it happened a lot sooner. Below are pastebin links to the logs. Please let me know if there are any other logs I should be looking at to troubleshoot this? Thank you.
I have been thinking about switching the OS to CentOS for some time now. I’ve decided to go for it since I had some free time and this issue was making it unreliable anyway. The setup was a little more challenging than it was with Ubuntu, just had to read up on SElinux. It has been running stable now for over 25 hours. Would have been longer but had to shutdown to add a second LAN card to the system.