Closed gudvinr closed 4 months ago
I don't understand the issue here. Bazarr require the RAR archive utility to work. It simply raise an exception and we send the exception stack to log. There's no spam in this.
It raises exception, exits, tries to start again, again raises exception, etc
Strictly specking, bazarr itself doesn't even need unrar to launch.
From source code I see that only few providers use unrar. None of which are enabled in my installation.
It raises exception, exits, tries to start again, again raises exception, etc
I'm unable to reproduce this behaviour. It raise exception and exit. How do you run Bazarr?
Strictly specking, bazarr itself doesn't even need unrar to launch. From source code I see that only few providers use unrar. None of which are enabled in my installation.
Although it's not strictly required if you don't enable specific providers, we took a design decision to make it mandatory to simplify code base. We have no plan to change that decision.
I'm unable to reproduce this behaviour. It raise exception and exit. How do you run Bazarr?
Yes, it does just exit. But it would be safe to say that virtually nobody runs daemons by hand as one-shot application.
People would use some kind of management tool. Docker, systemd, upstart, etc, windows service, plain autostart .desktop files, etc
I use docker, thus container gets restarted because of application exiting.
And that would be the same for basically any other management tool.
Although it's not strictly required if you don't enable specific providers, we took a design decision to make it mandatory to simplify code base. We have no plan to change that decision.
It still shouldn't stop from launching self-hosted (!) service because URL to download said tool is unavailable. Simply because it can be retried until success, executed in background and have some sort of resiliency against network errors.
Or, if unrar is not available on the system and can't be downloaded, exception can be thrown when unrar is used instead. And download can be logged as a warning and not cause hard failure.
You would prefer if it just hang their instead of existing when exception is raised? Your docker image provider should already have included the required a supported unrar tools. If not, it's definitely not one of our supported images providers (LSIO or Hotio).
I don't want to have to deal with missing unrar tools later in multiple places. I've decided that it's mandatory so if it's not installed, Bazarr will just wont start. If it's already installed or if it's available in the Bazarr bin directory, Bazarr will start even if there's no internet connection. Again, it's a non-issue once you've installed the requirement.
If there's something else to discuss here, let me know.
Describe the bug
If there's no internet access, bazarr instance fails to launch and ends up in inaccessible state.
To Reproduce Steps to reproduce the behavior:
Expected behavior Bazarr starts. Although it won't be able to fetch subtitles, at least it won't spam logs with errors and won't restart endlessly.
Screenshots
If applicable, add screenshots to help explain your problem.Software (please complete the following information):
Radarr version [e.g. v 0.2.0.0001]Sonarr version [e.g. v 2.0.0.0001]Additional context