AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Sonarr service unavailable11/20/2023 I've matched this up to my Radarr service file and it's the exact same except for it pointing to nzbdrone instead of radarr of course. Both the group and user exists, the user is assigned to the group as well. Looking at the errors it seems something to do with the group. Jun 18 12:04:52 server-desktop systemd: Failed to start Sonarr Daemon.ĮxecStart=/usr/bin/mono /opt/NzbDrone/NzbDrone.exe -nobrowser Jun 18 12:04:52 server-desktop systemd: rvice: Failed with result 'exit-code'. Jun 18 12:04:52 server-desktop systemd: rvice: Start request repeated too quickly. Jun 18 12:04:52 server-desktop systemd: Stopped Sonarr Daemon. Jun 18 12:04:52 server-desktop systemd: rvice: Scheduled restart job, restart counter is at 5. Jun 18 12:04:52 server-desktop systemd: rvice: Service hold-off time over, scheduling restart. Main PID: 6158 (code=exited, status=216/GROUP) Process: 6158 ExecStart=/usr/bin/mono /opt/NzbDrone/NzbDrone.exe -nobrowser (code=exited, status=216/GROUP) Loaded: loaded (/etc/systemd/system/rvice enabled vendor preset: enabled)Īctive: failed (Result: exit-code) since Tue 12:04:52 EDT 1s ago Here is a result of sudo systemctl status rvice rvice - Sonarr Daemon You are receiving this because you commented.I've tried to figure this out for months but am getting no where with Sonarr running as a service. You canĪlso copy the whole curl call there. Press on the reactivate button, the correct API url will be shown. Rightclick anywhere, click Inspect and then go to the Network tab. Parameters by going to the site where the button is displayed, then do a If the old Sonarr disables indexers and has aīutton to reactivate them, you can easily find out the appropriate URL and At least when I got an error, Iĭid not see any indication in the logs that the indexer would be disabled.Īlso, I do not see any button to restore the indexer, like in Sonarr. In Radarr so would only solve half the issue. One workaround would be to call the testall function every 15 or soĬurl ' ' -X POST -H 'Content-Length: 0' -H 'X-Api-Key: YOUR_API_KEY_HERE'Įdit: I think I determined the issue, I do not have the alpha v3 so I Instructions, I was able to copy the curl command and execute it. I just go into the indexer and retest it. This is on Chrome, but on Firefox its nearly the same. You can also copy the whole curl call there. If you press on the reactivate button, the correct API url will be shown there in the Network list. If the old Sonarr disables indexers and has a button to reactivate them, you can easily find out the appropriate URL and parameters by going to the site where the button is displayed, then do a rightclick anywhere, click Inspect and then go to the Network tab. Also, I do not see any button to restore the indexer, like in Sonarr. At least when I got an error, I did not see any indication in the logs that the indexer would be disabled. I also assume this command would not be in Radarr so would only solve half the issue. Any ideas?Įdit: I think I determined the issue, I do not have the alpha v3 so I guess it isn't in the original api. Hey I tried this and says that api call isn't found. One workaround would be to call the testall function every 15 or so minutes:Ĭurl '' -X POST -H 'Content-Length: 0' -H 'X-Api-Key: YOUR_API_KEY_HERE'
0 Comments
Read More
Leave a Reply. |