Sonarr on Synology Fails to Restart

Sonarr version (exact version): 20180303-13
Mono version (if Sonarr is not running on Windows): 5.8.0.108-11 (SynoCommunity Version)
OS: Synology DSM 6.2-23739 (DS415play)
Debug logs: https://pastebin.com/p839uPri
Description of issue:
When restarting Sonarr, it shuts down but fails to restart due to another instance running.

I can SSH in and kill the process and then manually start Sonarr. I’ve checked and I’ve seen other people with the issue but I haven’t been able to resolve. I’ve uninstalled Mono + Sonarr and then reinstalled and that can consistently get it back working again but, without fail, as soon as I try to restart Sonarr, the above issue in the log happens.

Frankly, some of the solutions involving a beta version of Mono are confusing and I think this is because they are aged and no longer applicable due to updates.

It seems Sonarr is still running and not exiting, it may be that the Synology package is restarting the process when Sonarr attempts to restart it. If you press shutdown instead of restart does Sonarr actually restart?

If I hit “Shutdown” in Sonarr, it never shows as “stopped” in Synology (even though I can no longer access Sonarr as normal).

If I check for processes via SSH, This is the result (after “ps -ef | grep nzbdrone” command):

sc-nzbd+ 15494 1 93 16:53 ? 00:00:29 /usr/local/mono/bin/mono /volume1/@appstore/nzbdrone/share/NzbDrone/NzbDrone.exe

With this process, I am able to hit “stop” in the Synology GUI package center because Sonarr still shows as running. From there, I can see (via the same above command) that the process stops, and then shows as “Stopped” in Synology. I can then start it back up again and it starts without issue.

I’ve done some research and in 2017 there was a similar issue and the solution involved a beta release of Mono and updating the Mono path in the start-stop-status script. There is information regarding that solution here: https://forum.synology.com/enu/viewtopic.php?t=122376 I wonder if this problem is something similar. We’re getting beyond my troubleshooting capability though. I’ve poked around in the files listed in the solution above and I think they have changed too much for that solution to be 100% relevant to this issue.

Sounds like the package doesn’t really stop properly when Sonarr stops within it. Could be a mono thing or something with the package, but that package isn’t maintained by us.

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