-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonarr remains inactive, after fix isn't reachable through reverse proxy #293
Comments
I tried tunneling over ssh to the media server
So whilst sonarr is running, the webserver is refusing to connect on port 8989. So does sonarr spawn its own webserver? Or is atk responsible for that? |
Ok, so the sonarr database was corrupted. After restoring to another backup it works as expected. So while that's not got anything to do with atk, other parts in the process (such as having to manually install nzbdrone) should probably be caught by atk. So my particular issue was resolved, but hopefully atk could catch some of these things automatically in the future. Hope this helps! |
The problem
I restarted sonarr from the sonarr web interface. It went down but never came back up. After waiting for a while, I reinstalled it (keeping configuration settings), still remains inactive. Then I reinstalled without keeping configuration settings, still inactive.
When reinstalling the logs are:
systemctl status sonarr.service
yields:When trying to run the start command for sonarr manually (
/usr/bin/mono /opt/NzbDrone/NzbDrone.exe -nobrowser
) the error is:Checking /opt with
ls -l /opt
:So it's not there. Attempting a manual install with
sudo apt-get install nzbdrone
:Manually installed and restarted it with:
On reboot it now starts as expected, but still isn't accessible from another computer. Running access details from atk yields:
Any idea why other local devices cannot connect to the service? Other services on the same device, like radarr and nzbget can be reached without problems.
My Linux distribution and version is:
Ubuntu Server 16.04.4 LTS
I'm seeing this behaviour on:
I'm not a dummy, so I've checked these!
The text was updated successfully, but these errors were encountered: