Sonarr version (exact version): 2.0.0.5228
Mono version (if Sonarr is not running on Windows): 4.2.1
OS: Ubuntu 16.04
Debug logs: https://tinyurl.com/ybe5t4f5 (journalctl)
Description of issue: I’ve followed to autostart guide for Debian outline here: https://github.com/Sonarr/Sonarr/wiki/Autostart-on-Debian. Did everything exactly as described (except follow the steps in the security note, but those appear to be optional). When I get to the step to actually start created service (“sudo service nzbdrone start”), it fails. Sonarr is not running. What am I doing wrong?
Looks like you’re mixing and matching init.d and systemd. systemd is the better way to do it, https://github.com/Sonarr/Sonarr/wiki/Autostart-on-Linux#systemd
Hey! Thanks for the reply. I switched to the systemd method after the init.d method didn’t work. Since it’s mixed and matched now (with neither one working), would it make sense to undo all changes I’ve made (for both methods) and start fresh? And, if so, how do I do that? I had that thought initially (that I might have created a conflict on top of everything now), but couldn’t find any clear documentation how to reverse either.
Starting from scratch would be good, deleting the init.d and systemd files you created would be a good first step to start from scratch, not sure if there is anything else necessary.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.