Sonarr version: 3.0.2
Mono version: 6.6.0.161
OS: Lubuntu 18.04
Debug logs: N/A. None generated.
Description of issue:
I should probably disclaim the fact that I’m likely doing something stupid, but hopefully someone will be kind enough to let me down easy.
Up until this morning I was running v3 quite happily and it worked like a bomb. Had a power outage and after power up afterwards, Sonarr wouldn’t start. service status was ambiguous:
● sonarr.service - Sonarr Daemon
Loaded: loaded (/etc/systemd/system/sonarr.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-02-16 21:06:58 SAST; 3s ago
Process: 26918 ExecStart=/usr/bin/mono --debug /opt/NzbDrone/NzbDrone.exe -nobrowser (code=exited, status=2)
Main PID: 26918 (code=exited, status=2)
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Service hold-off time over, scheduling restart.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Scheduled restart job, restart counter is at 5.
Feb 16 21:06:58 media-laptop systemd[1]: Stopped Sonarr Daemon.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Start request repeated too quickly.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Failed with result 'exit-code'.
Feb 16 21:06:58 media-laptop systemd[1]: Failed to start Sonarr Daemon.
So I tried manually starting it with /usr/bin/mono --debug /opt/NzbDrone/NzbDrone.exe -nobrowser only to receive a No such file or directory error. It didn’t take long to figure out that the whole /opt/NzbDrone folder didn’t exist. I removed everything and started from scratch with a fresh Sonarr install. At the end of it the same thing happened: the service wouldn’t start and no /opt/NzbDrone folder.
I then decided to follow my original route by installing v2 first and upgrading. v2 installed fine and worked perfectly and the /opt/NzbDrone folder was in place. I then installed Sonarr only to find that folder had again been removed during the install process and the Sonarr service wouldn’t start.
Going back to my initial disclaimer, I fully expect someone to tell me that this is by design and I’ve overlooked something obvious, but I’d rather hear it directly than fumble around endlessly trying to figure it out.
Sonarr isn’t generating logs, which makes me think it isn’t installing properly (~/.config/NzbDrone/logs/sonarr.txt only contains old entries). All I end up with is the usual syslog entry:
Feb 16 21:06:58 media-laptop systemd[1]: Started Sonarr Daemon.
Feb 16 21:06:58 media-laptop mono[26918]: Cannot open assembly '/opt/NzbDrone/NzbDrone.exe': No such file or directory.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Failed with result 'exit-code'.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Service hold-off time over, scheduling restart.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Scheduled restart job, restart counter is at 5.
Feb 16 21:06:58 media-laptop systemd[1]: Stopped Sonarr Daemon.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Start request repeated too quickly.
Feb 16 21:06:58 media-laptop systemd[1]: sonarr.service: Failed with result 'exit-code'.
Feb 16 21:06:58 media-laptop systemd[1]: Failed to start Sonarr Daemon.
Anyone with the patience to offer some advice, I’d appreciate it tremendously.
[edit] I should add that in each case I’ve followed the site installation instructions to the letter.