Project

General

Profile

Bug #2385

Issue starting sonarr

Added by modem7 7 days ago. Updated 6 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/12/2019
Due date:
% Done:

0%


Description

Hey guys,

I changed Sonarr settings to try and get reverse proxy working (changed enable SSL + URL base as per https://github.com/Sonarr/Sonarr/wiki/Reverse-Proxy) and now it seems that Sonarr refuses to start.
Getting the following:

Redirecting to /bin/systemctl status sonarr.service
● sonarr.service - Sonarr Daemon
Loaded: loaded (/usr/lib/systemd/system/sonarr.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2019-03-09 20:58:40 GMT; 37s ago
Process: 16575 ExecStart=/usr/bin/mono /var/hda/web-apps/sonarr/html/NzbDrone.exe -nobrowser -data /var/hda/web-apps/sonarr (code=exited, status=1/FAILURE)
Main PID: 16575 (code=exited, status=1/FAILURE)

Mar 09 20:58:38 localhost.localdomain systemd[1]: Started Sonarr Daemon.
Mar 09 20:58:39 localhost.localdomain mono[16575]: Press enter to exit...
Mar 09 20:58:40 localhost.localdomain systemd[1]: sonarr.service: Main process exited, code=exited, status=1/FAILURE
Mar 09 20:58:40 localhost.localdomain systemd[1]: sonarr.service: Unit entered failed state.
Mar 09 20:58:40 localhost.localdomain systemd[1]: sonarr.service: Failed with result 'exit-code'.

Do we know where the location of the config.xml for sonarr lives (version installed via the amahi app store) to see if I can revert some files?

If I run "/usr/bin/mono /var/hda/web-apps/sonarr/html/NzbDrone.exe -nobrowser -data /var/hda/web-apps/sonarr" sonarr starts, but it doesn't seem to load it's database.
Further note: Nginx is loaded on a raspberry pi, so no direct changes apart from the above have been done to the Amahi installation.
Worst case, where is it that Amahi's Sonarr install keeps it's backups? I know my Radarr install keeps it in /home/radarr/.config/Radarr/Backups/scheduled/

History

#1 Updated by modem7 7 days ago

OK, here's what I've done so far:

I've managed to finally find the backup locations (thankfully one made 5 days ago).
Uninstalled
Reinstalled

Sonarr doesn't start via service, comes up with following error:


Redirecting to /bin/systemctl status sonarr.service
● sonarr.service - Sonarr Daemon
Loaded: loaded (/usr/lib/systemd/system/sonarr.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-03-10 00:32:28 GMT; 1s ago
Process: 20844 ExecStart=/usr/bin/mono /var/hda/web-apps/sonarr/html/NzbDrone.exe -nobrowser -data /var/hda/web-apps/sonarr (code=exited, status=1/FAILURE)
Main PID: 20844 (code=exited, status=1/FAILURE)

Mar 10 00:32:26 localhost.localdomain systemd[1]: Started Sonarr Daemon.
Mar 10 00:32:27 localhost.localdomain mono[20844]: Press enter to exit...
Mar 10 00:32:28 localhost.localdomain systemd[1]: sonarr.service: Main process exited, code=exited, status=1/FAILURE
Mar 10 00:32:28 localhost.localdomain systemd[1]: sonarr.service: Unit entered failed state.
Mar 10 00:32:28 localhost.localdomain systemd[1]: sonarr.service: Failed with result 'exit-code'.

It does however, now start (with the correct settings + database) if I do: /usr/bin/mono /var/hda/web-apps/sonarr/html/NzbDrone.exe -nobrowser -data /var/hda/web-apps/sonarr

#2 Updated by modem7 7 days ago

If I uninstall Sonarr from amahi, and install it myself, I'm now getting the following error:

sonarr.service - Sonarr Daemon
Loaded: loaded (/usr/lib/systemd/system/sonarr.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-03-10 16:18:11 GMT; 3s ago
Process: 11649 ExecStart=/usr/bin/mono /opt/NzbDrone/NzbDrone.exe -nobrowser -data /opt/NzbDrone (code=exited, status=2)
Main PID: 11649 (code=exited, status=2)
Mar 10 16:18:08 localhost.localdomain mono11649: [Info] OwinHostController: http://*:8989/sonarr/
Mar 10 16:18:08 localhost.localdomain mono11649: [Info] OwinHostController: http://*:8989/
Mar 10 16:18:08 localhost.localdomain mono11649: [Info] OwinHostController: https://*:443/sonarr/
Mar 10 16:18:08 localhost.localdomain mono11649: [Info] OwinHostController: https://*:443/
Mar 10 16:18:09 localhost.localdomain mono11649: [Info] NancyBootstrapper: Starting Web Server
Mar 10 16:18:09 localhost.localdomain mono11649: [Fatal] ConsoleApp: Access denied. This can happen if another instance of Sonarr is already running another application is using the same port (default: 8989) or the user has insufficient permissions
Mar 10 16:18:09 localhost.localdomain mono11649: Press enter to exit...
Mar 10 16:18:11 localhost.localdomain systemd1: sonarr.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 10 16:18:11 localhost.localdomain systemd1: sonarr.service: Unit entered failed state.
Mar 10 16:18:11 localhost.localdomain systemd1: sonarr.service: Failed with result 'exit-code'.

sudo netstat -tulpn | grep :8989 shows nothing in this case, so it looks like it's permissions?

#3 Updated by modem7 6 days ago

Interesting thing I'm noting:

If I run the process manually, I get the following:

[Info] OwinHostController: Listening on the following URLs:
[Info] OwinHostController: http://*:8989/

If I run it as a service, I get the following:

Mar 12 17:57:26 localhost.localdomain mono26469: [Info] OwinHostController: http://*:8989/sonarr/
Mar 12 17:57:26 localhost.localdomain mono26469: [Info] OwinHostController: http://*:8989/
Mar 12 17:57:26 localhost.localdomain mono26469: [Info] OwinHostController: https://*:443/sonarr/
Mar 12 17:57:26 localhost.localdomain mono26469: [Info] OwinHostController: https://*:443/

#4 Updated by modem7 6 days ago

  • Status changed from New to Closed

Resolved by editing alternative config file in sonarr home directory

Also available in: Atom