Hi,
I went from SickBeard to Sonarr last day and wanted to give it a shoot but unfortenaly Sonarr crashes time to time for me. It start to work again if I reboot my machine.
If anyone could help me it would be lovely because I’m pretty new to Linux/Ubuntu so I’m having a hard time when I’m reading the logs.
OS: 14.04.1-Ubuntu Server LTS
Sonarr: 2.0.0.3004
Mono Version: 3.12.1
Amount of series: 7
Amount of indexers: 8
The DB lock (2nd error) is the only one of limited value though Sonarr only uses limited locks on its database. Are you seeing a large number of DB locks?
You should be running mono with the --debug switch, without it, error messages are mostly useless as they don’t show where the error happened.
I have the same issue: sonarr crashes very often. I use the same OS, mono version and I believe the same sonarr version. I would like to attach my logs here, run using the debug switches, but don’t see how.
Now I see that pastebin has deleted my logs. I don’t know why. Maybe it doesn’t matter, since I am not sure which of the few dozen logs on my system are useful. It is too bad, because it has become completely unstable, and crashes every day. This makes it too unreliable to use.
Here are my logs for the same problem on the same OS and version numbers:
EDIT: I guess there is no solution, so will need to abandon sonarr unfortunately. Too bad, because I liked it when it worked. It just doesn’t run for longer than a few hours anymore.
That is a good point: it does not restart, even though it is a demon. Here is what the crash looks like when I run from CLI using --debug on mono. It is also edited because of sonarr forum rules about links: http-> ptth
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
I’m running mono 3.8.0 on unraid (Slackware) and I’m getting this too for the last week or so. The sonar logs show no indication to the issue. I might have to delete the config directory and start from scratch .