Constant database corruption and crashing

Running the latest version of OpenMediaVault and the latest version of Sonarr installed through OMV’s app repository, working on the master branch (currently). Sonarr will crash and become unresponsive, requiring a reboot to restart. Once it does, it works fine for ~20 minutes.

If I attempt to restart from the CL interface, it tells me that there is an epic failure and that there is a sqlite database corruption error. I completely uninstalled Sonarr, removed all traces of it on the system, and then tried to reinstall… twice.

It hasn’t solved the issue.

What else can I do?

Sonarr has a separate AppData folder, outside of the installation location. Typically its in /home/<user>/.config/NzbDrone, where <user> is the username of the user running Sonarr, but could be different on your system (you should be able to search for nzbdrone.db to find the location).

Which version of mono is installed?

On OMV sonarr runs as the sonarr user, so I made sure to rm -rf that whole folder.

I think it was 3.10 for mono. I originally installed it from a Tarball instead of through OMV’s official repo because, at the time, there was no official OMV version of nzbdrone. and I thought that might be the issue, so I uninstalled mono. My internet connection died shortly after so I haven’t been able to reinstall sonarr but I’ll try it later today with a fresh version of mono.

Spoke too soon. Still randomly crashes, even with a fresh build of mono and everything. I’m going to try switching over to the developer branch and see if they have a fix.

Tried a complete reinstall of my OS and Sonarr. Running the developer branch still, crashes still happen. No clue as to what is going on.

Which version on mono are you running now?

3.12.

I’m running Sonarr under OpenMediaVault, and that’s the version that gets pulled whenever I install the plugin through their interface (generally a better idea that complining on my own). I understand, however, that there may be some issues with 3.12? Is there a way I can, for lack of a better word, “downgrade” my Mono to 3.10?

There was a rather large issue with 3.12 when it was first released, but that has been resolved. I don’t think we have enough of a user base on 3.12 to make a decision whether or not there is a stability issue as well.

Unfortunately I’m not aware of a way to downgrade on OMV, in fact I’m not familiar with that system.

When it does crash what do the logs say?

I think I can probably just recompile Mono as 3.10 from a tarball and then link Sonarr to it, but that seems like a lot of hassle for something that will likely be fixed in a month or so.

Edit: I can’t get logs because by the time I notice it is down, I have to reboot to make it responsive and that clears the logs.

Rebooting clears the logs? Thats not something Sonarr does, you can access the logs right from the file system their in a logs folder in Sonarr’s AppData folder (visible on System -> Info).

Did not know that. Here’s a pastebin of the log.

http://pastebin.com/1wChLebq

Not seeing anything in the logs, do they cover the time of a crash?

I have the same problem. The log snippet is:

15-2-3 06:37:43.1|Info|SeriesSearchService|Series search completed. 0 reports downloaded.
15-2-3 06:50:26.0|Info|RssSyncService|Starting RSS Sync
15-2-3 06:50:29.0|Info|DownloadDecisionMaker|Processing 300 reports
15-2-3 06:50:30.8|Info|RssSyncService|RSS Sync Completed. Reports found: 300, Reports grabbed: 0
15-2-3 07:05:42.0|Info|RssSyncService|Starting RSS Sync
15-2-3 07:05:50.7|Info|DownloadDecisionMaker|Processing 300 reports
15-2-3 07:05:51.9|Info|RssSyncService|RSS Sync Completed. Reports found: 300, Reports grabbed: 0
15-2-3 07:21:17.2|Info|RssSyncService|Starting RSS Sync
15-2-3 07:21:26.7|Info|DownloadDecisionMaker|Processing 300 reports
15-2-3 07:21:27.8|Info|RssSyncService|RSS Sync Completed. Reports found: 300, Reports grabbed: 0
15-2-3 13:25:06.6|Info|Bootstrap|Starting NzbDrone - /home/fiji/NzbDrone/NzbDrone.exe - Version 2.0.0.2722
15-2-3 13:25:06.9|Debug|ProcessProvider|Found 0 processes with the name: NzbDrone.Console
15-2-3 13:25:07.0|Debug|ProcessProvider|Found 1 processes with the name: NzbDrone

I restarted it at 13:25, it crashed when there was apparently nothing going on. It crashes every few hours since an update sometime last week. Before that it had been working like a champ.

I’m on Fedora release 20 (Heisenbug) with ‘Mono JIT compiler version 3.12.0 (tarball Mon Jan 19 15:51:05 GMT 2015)’

Thanks!
-ben

That’s the log from the file, so it should, unless there’s something that wipes the logs, like a system reboot (which I can’t remember if I did).

I’m having a similar error with Sonarr on OMV crashing every so often. I know this post is quite old, so hoping someone came across a solution.

OMV v. 2.1.1
Sonarr v. 2.0.0.3357
Mono v. 4.0.2

Same as above, there is nothing evident in the log when Sonarr crashes – the last entry on the most recent crash was “RSS Sync Completed”.

Anyone find a fix?