Hi,
I have been running sonarr on my ubuntu dedi for years (or so) and never had any problems until a couple of days ago.
It just stops. Nothing in the logs, no trace, I just try to contact it and it’s gone, the process not found in top. When I start it again it’s back without issues, then it works a couple of days, then it’s gone.
Any ideas? I’m running the latest version from develop branch using an init.d script.
Recently do a kernel update?
“For every action there is an equal and opposite reaction.”
We’ve had quite a few reports about odd crashes, most of them known to be so called Native crashes, where mono cries out in terror and dies without telling us why.
Initially this thread was to collect important information about the systems on which the crashes occurred.
Since this thread was posted I’ve literally spent more than a hundred hours investigating this issue.
Debugging Sonarr and mono countless times, compiled mono half …
I’m getting the (another?) native mono crash again with version Sonarr 2.0.0.3328 (July 16, 2015 build) on a current kernel.
systemctl status sonarr -l
● sonarr.service - Sonarr Daemon
Loaded: loaded (/usr/lib/systemd/system/sonarr.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2015-07-16 08:28:30 EDT; 3min 54s ago
Process: 3120 ExecStart=/usr/bin/mono /opt/NzbDrone/NzbDrone.exe -nobrowser (code=exited, status=0/SUCCESS)
Main PID: 3120 (code=exited, status=…
Also make sure you’re using mono 3.10 or higher (4.2.1 is the latest).
Hey,
haven’t updated in a while. Kernel version is 3.19.0-26-generic, mono version is 3.10.
I’m now running sonarr in tmux, hoping that I get some output there.
Taloth
January 13, 2016, 6:46pm
4
fyi, upstart outputs console logs in /var/log/upstart/nzbdrone.log
system
Closed
March 13, 2016, 6:47pm
5
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.