Servarr - User contributions [en]

https://wikiold.servarr.com/api.php?action=feedcontributions&feedformat=atom&user=Ta264 Servarr - User contributions [en] 2026-05-18T22:35:04Z User contributions MediaWiki 1.35.2 https://wikiold.servarr.com/index.php?title=System_status&diff=3203 System status 2021-02-23T09:07:28Z

<p>Ta264: </p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET. We provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> *** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop radarr</code> Stop Radarr<br /> ****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries<br /> **** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball<br /> **** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries<br /> **** <code> sudo chown radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory<br /> **** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries<br /> **** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> ***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start radarr.service</code> Restart Radarr<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run on BSD and very old ARM processors. <br /> ** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span><br /> ** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> * For Caddy (V1) use this:<br /> ** Note: you'll also need to add the websocket directive to your radarr configuration<br /> proxy /radarr 127.0.0.1:7878 {<br /> websocket<br /> transparent<br /> }<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="currently_installed_net_framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_net_framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''</span><br /> ****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr<br /> ****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball<br /> ****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries<br /> ****<code> sudo chown lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> ***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start lidarr.service</code> Restart Lidarr<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop readarr</code> Stop Readarr<br /> ****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball<br /> ****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries<br /> ****<code> sudo chown readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Raedarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> ***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start readarr.service</code> Restart Readarr<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code>and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code>and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client.<br />Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occasionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occasionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occasionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occasionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> * <span id="import_list_missing_root_folder">'''[[#import_list_missing_root_folder|Import List missing root folder]]'''</span><br /> ** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.<br /> **#Go to Settings > Import Lists<br /> **#Edit the import lists that were mentioned in the health check<br /> **#Save<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home Page: [https://radarr.video Radarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Radarr You're here already]<br /> * Reddit: [https://reddit.com/r/radarr r/radarr]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://sonarr.tv Sonarr's home page]<br /> * Forums: [https://forums.sonarr.tv Sonarr Forums]<br /> * Discord: [https://discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr r/sonarr]<br /> * Twitter: [https://twitter.com/sonarrtv @sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com/sonarr You're here already]<br /> * Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]<br /> * Source: https://github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [https://lidarr.audio Lidarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Lidarr You're here already]<br /> * Reddit: [https://reddit.com/r/lidarr r/lidarr]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]<br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Readarr You're here already]<br /> * Reddit: [https://reddit.com/r/readarr r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=3202 System status 2021-02-23T09:06:59Z

<p>Ta264: </p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET. We provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> *** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop radarr</code> Stop Radarr<br /> ****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries<br /> **** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball<br /> **** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries<br /> **** <code> sudo chown radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory<br /> **** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries<br /> **** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> ***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start radarr.service</code> Restart Radarr<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run on BSD and very old ARM processors. <br /> ** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span><br /> ** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> * For Caddy (V1) use this:<br /> ** Note: you'll also need to add the websocket directive to your radarr configuration<br /> proxy /radarr 127.0.0.1:7878 {<br /> websocket<br /> transparent<br /> }<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="currently_installed_net_framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_net_framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''</span><br /> ****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr<br /> ****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball<br /> ****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries<br /> ****<code> sudo chown lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> ***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start lidarr.service</code> Restart Lidarr<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> **** For a x64 install you'd use <code>wget --content-disposition [https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 'https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64][http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64' ']</code><br /> ***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop readarr</code> Stop Readarr<br /> ****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball<br /> ****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries<br /> ****<code> sudo chown readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Raedarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> ***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start readarr.service</code> Restart Readarr<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code>and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code>and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client.<br />Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occasionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occasionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occasionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occasionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> * <span id="import_list_missing_root_folder">'''[[#import_list_missing_root_folder|Import List missing root folder]]'''</span><br /> ** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.<br /> **#Go to Settings > Import Lists<br /> **#Edit the import lists that were mentioned in the health check<br /> **#Save<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home Page: [https://radarr.video Radarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Radarr You're here already]<br /> * Reddit: [https://reddit.com/r/radarr r/radarr]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://sonarr.tv Sonarr's home page]<br /> * Forums: [https://forums.sonarr.tv Sonarr Forums]<br /> * Discord: [https://discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr r/sonarr]<br /> * Twitter: [https://twitter.com/sonarrtv @sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com/sonarr You're here already]<br /> * Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]<br /> * Source: https://github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [https://lidarr.audio Lidarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Lidarr You're here already]<br /> * Reddit: [https://reddit.com/r/lidarr r/lidarr]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]<br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Readarr You're here already]<br /> * Reddit: [https://reddit.com/r/readarr r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=3201 System status 2021-02-23T09:06:27Z

<p>Ta264: </p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET. We provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ****For a x64 install you'd use <code>wget --content-disposition 'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</code><br /> *** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop radarr</code> Stop Radarr<br /> ****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries<br /> **** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball<br /> **** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries<br /> **** <code> sudo chown radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory<br /> **** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries<br /> **** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> ***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start radarr.service</code> Restart Radarr<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run on BSD and very old ARM processors. <br /> ** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span><br /> ** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> * For Caddy (V1) use this:<br /> ** Note: you'll also need to add the websocket directive to your radarr configuration<br /> proxy /radarr 127.0.0.1:7878 {<br /> websocket<br /> transparent<br /> }<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="currently_installed_net_framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_net_framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''</span><br /> ****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr<br /> ****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball<br /> ****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries<br /> ****<code> sudo chown lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> ***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start lidarr.service</code> Restart Lidarr<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> **** For a x64 install you'd use <code>wget --content-disposition [https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 'https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64][http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64' ']</code><br /> ***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop readarr</code> Stop Readarr<br /> ****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball<br /> ****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries<br /> ****<code> sudo chown readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Raedarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> ***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start readarr.service</code> Restart Readarr<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code>and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code>and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client.<br />Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occasionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occasionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occasionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occasionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> * <span id="import_list_missing_root_folder">'''[[#import_list_missing_root_folder|Import List missing root folder]]'''</span><br /> ** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.<br /> **#Go to Settings > Import Lists<br /> **#Edit the import lists that were mentioned in the health check<br /> **#Save<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home Page: [https://radarr.video Radarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Radarr You're here already]<br /> * Reddit: [https://reddit.com/r/radarr r/radarr]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://sonarr.tv Sonarr's home page]<br /> * Forums: [https://forums.sonarr.tv Sonarr Forums]<br /> * Discord: [https://discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr r/sonarr]<br /> * Twitter: [https://twitter.com/sonarrtv @sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com/sonarr You're here already]<br /> * Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]<br /> * Source: https://github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [https://lidarr.audio Lidarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Lidarr You're here already]<br /> * Reddit: [https://reddit.com/r/lidarr r/lidarr]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]<br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Readarr You're here already]<br /> * Reddit: [https://reddit.com/r/readarr r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=3200 System status 2021-02-23T09:03:04Z

<p>Ta264: </p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET. We provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ****For a x64 install you'd use <code>wget --content-disposition 'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</code><br /> *** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop radarr</code> Stop Radarr<br /> ****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries<br /> **** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball<br /> **** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries<br /> **** <code> sudo chown radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory<br /> **** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries<br /> **** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> ***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start radarr.service</code> Restart Radarr<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run on BSD and very old ARM processors. <br /> ** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span><br /> ** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> * For Caddy (V1) use this:<br /> ** Note: you'll also need to add the websocket directive to your radarr configuration<br /> proxy /radarr 127.0.0.1:7878 {<br /> websocket<br /> transparent<br /> }<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="currently_installed_net_framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_net_framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> *** For a x64 install you'd use <code>wget --content-disposition 'https://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64'</code><br /> ***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''</span><br /> ****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr<br /> ****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball<br /> ****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries<br /> ****<code> sudo chown lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> ***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start lidarr.service</code> Restart Lidarr<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> **** For a x64 install you'd use <code>wget --content-disposition [https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 'https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64][http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64' ']</code><br /> ***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> ****<code> sudo systemctl stop readarr</code> Stop Readarr<br /> ****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries<br /> ****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball<br /> ****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries<br /> ****<code> sudo chown readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory<br /> ****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries<br /> ****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball<br /> **** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Raedarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> ***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.<br /> ****<code> systemctl daemon-reload</code> Reload the Systemd Files<br /> ****<code> sudo systemctl start readarr.service</code> Restart Readarr<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is use of a nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code>and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code>and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code>all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client.<br />Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occasionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occasionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occasionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occasionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> * <span id="import_list_missing_root_folder">'''[[#import_list_missing_root_folder|Import List missing root folder]]'''</span><br /> ** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.<br /> **#Go to Settings > Import Lists<br /> **#Edit the import lists that were mentioned in the health check<br /> **#Save<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.<br /> ***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space within your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home Page: [https://radarr.video Radarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Radarr You're here already]<br /> * Reddit: [https://reddit.com/r/radarr r/radarr]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://sonarr.tv Sonarr's home page]<br /> * Forums: [https://forums.sonarr.tv Sonarr Forums]<br /> * Discord: [https://discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr r/sonarr]<br /> * Twitter: [https://twitter.com/sonarrtv @sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com/sonarr You're here already]<br /> * Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]<br /> * Source: https://github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [https://lidarr.audio Lidarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Lidarr You're here already]<br /> * Reddit: [https://reddit.com/r/lidarr r/lidarr]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]<br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Wiki: [https://wiki.servarr.com/Readarr You're here already]<br /> * Reddit: [https://reddit.com/r/readarr r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=3068 System status 2021-01-25T17:57:23Z

<p>Ta264: /* System Warnings */</p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> *** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run on BSD and very old ARM processors. <br /> ** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span><br /> ** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> * For Caddy (V1) use this:<br /> ** Note: you'll also need to add the websocket directive to your radarr configuration<br /> proxy /radarr 127.0.0.1:7878 {<br /> websocket<br /> transparent<br /> }<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="currently_installed_net_framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> <br /> * <span id="currently_installed_net_framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> *** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> *** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished movie is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDbId that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Reddit: [htttps://reddit.com/r/radarr]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Forums: [forums.sonarr.tv Official Sonarr Forums]<br /> * Discord: [discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr]<br /> * Twitter: [@sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]<br /> * Source: [github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [lidarr.audio Lidarr's home page]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] <br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Reddit: [https://reddit.com/r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=3067 System status 2021-01-25T17:53:59Z

<p>Ta264: /* Radarr */</p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> *** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span><br /> ** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> * For Caddy (V1) use this:<br /> ** Note: you'll also need to add the websocket directive to your radarr configuration<br /> proxy /radarr 127.0.0.1:7878 {<br /> websocket<br /> transparent<br /> }<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="currently_installed_net_framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> <br /> * <span id="currently_installed_net_framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> <br /> * <span id="currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> *** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> *** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished movie is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDbId that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Reddit: [htttps://reddit.com/r/radarr]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Forums: [forums.sonarr.tv Official Sonarr Forums]<br /> * Discord: [discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr]<br /> * Twitter: [@sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]<br /> * Source: [github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [lidarr.audio Lidarr's home page]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] <br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Reddit: [https://reddit.com/r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=2850 System status 2020-12-22T16:53:34Z

<p>Ta264: </p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> *** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> ** Managed/tooled installs<br /> *** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/radarr/#migrating-to-v3-on-net-core Swizzin Docs article]<br /> *** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Radarr#radarr_v3_(unstable) WB Wiki article]<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> <br /> *<span id="updating_will_not_be_possible_to_prevent_deleting_appdata_on_update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within radarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:<br /> proxy_http_version 1.1;<br /> proxy_set_header Upgrade $http_upgrade;<br /> proxy_set_header Connection $http_connection;<br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> Include /etc/apache2/mods-available/proxy_wstunnel.load<br /> ProxyPass "/socket" "ws://127.0.0.1:7878/socket"<br /> ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"<br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> * <span id="Currently_installed_Net_Framework_is_old_and_unsupported">'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> <br /> * <span id="Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> <br /> * <span id="Currently_installed_mono_version_is_old_and_unsupported">'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="Currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> <br /> * <span id="New_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> * <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> <br /> * <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.<br /> *** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> ** Managed/tooled installs<br /> *** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/lidarr/#migrating-to-v3-on-net-core Swizzin Docs article]<br /> *** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Lidarr#lidarr(unstable) WB Wiki article]<br /> <br /> *<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span><br /> ** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=lidarr_system_status_health_system_warnings /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> *** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br /> ****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> ***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br /> ***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.<br /> *** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> ** Managed/tooled installs<br /> *** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/radarr/#migrating-to-v3-on-net-core Swizzin Docs article]<br /> *** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Radarr#radarr_v3_(unstable) WB Wiki article]<br /> <br /> *<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span><br /> ** Raedarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 5.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> <br /> *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> **''(This warning will not appear if your current version is less than 14 days old)''<br /> <br /> *<span id="cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.<br /> <br /> *<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> **'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> <br /> *<span id="could_not_connect_to_signalr">'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:<br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable-to-communicate-with-download-client|Unable to communicate with download client]]'''</span><br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker-bad-remote-path-mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Radarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Radarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Radarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=radarr_system_status_health_download_clients /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''</span><br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> <section end=sonarr_system_status_health_download_clients /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable-to-communicate-with-download-client|Unable to communicate with download client]]'''</span><br /> ** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Lidarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker-bad-remote-path-mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Lidarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished movie is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Lidarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Lidarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available">'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -&gt; Download Client.<br /> <br /> * <span id="unable_to_communicate_with_download_client">'''[[#unable-to-communicate-with-download-client|Unable to communicate with download client]]'''</span><br /> ** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> ** This is typically due to improperlly configured download client. Things you can typically check:<br /> *** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br /> *** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.<br /> *** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|here]] for more information on this one in our FAQ.<br /> <br /> * <span id="download_clients_are_unavailable_due_to_failure">'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Readarr to prevent the errors.<br /> <br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <br /> * <span id="docker_bad_remote_path_mapping">'''[[#docker-bad-remote-path-mapping|Docker bad remote path mapping]]'''</span><br /> ** This error is typically associated with bad docker paths within either your download client or Readarr<br /> *** An example of this would be:<br /> **** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br /> **** Readarr: <code>Download Path: /data:/mnt/user/downloads</code><br /> **** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br /> **** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br /> **** Team Readarr is a big fan of simply using <code>/data</code>.<br /> ***** Download client: <code>/data:/mnt/user/data</code><br /> ***** Readarr: <code>/data:/mnt/user/data</code><br /> ***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br /> *** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> **''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.<br /> ** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> * <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.<br /> ** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> * <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span><br /> ** Simply put you do not have any of your indexers set to allow automatic searches<br /> *** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.<br /> <br /> *<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''</span><br /> ** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]<br /> ** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync<br /> <br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Lidarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> * <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Readarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br /> <br /> * <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> <br /> * <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder<br /> ***# Easiest way to find this is to go to the Movies (Library) Tab<br /> ***# Create a custom filter with the old root folder path<br /> ***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files<br /> <section end=radarr_system_status_health_folders /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Series > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> * <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span><br /> ** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.<br /> *** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder<br /> ***# Go to the Library > Mass Editor Tab<br /> ***# Create a custom filter with the old root folder path <br /> ***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.<br /> ***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span><br /> ** The movie is linked to a TMDbId that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <br /> * <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span><br /> ** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> This will tell you about your current install of Lidarr<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> This will tell you about your current install of Readarr<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Reddit: [htttps://reddit.com/r/radarr]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Forums: [forums.sonarr.tv Official Sonarr Forums]<br /> * Discord: [discord.gg/M6BvZn5 Join our discord]<br /> * Reddit: [https://reddit.com/r/sonarr]<br /> * Twitter: [@sonarrtv]<br /> * IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]<br /> * Source: [github.com/Sonarr/Sonarr Github]<br /> * Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> * Home page: [lidarr.audio Lidarr's home page]<br /> * Discord: [https://discord.com/invite/5WQc3S8 Join our discord]<br /> * Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]<br /> * Source: [https://github.com/lidarr/Lidarr/ Github]<br /> * Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] <br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> * Home page: [https://readarr.com Readarr's home page]<br /> * Reddit: [https://reddit.com/r/readarr]<br /> * Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]<br /> * Source: [https://github.com/Readarr/Readarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=Template:Troubleshooting&diff=2742 Template:Troubleshooting 2020-12-17T10:33:29Z

<p>Ta264: </p> <hr /> <div><noinclude><br /> <templatedata><br /> {<br /> "params": {<br /> "ARRNAME": {<br /> "description": "Name of the Application",<br /> "example": "Radarr",<br /> "type": "string",<br /> "required": true<br /> },<br /> "ARR_DISCORD": {<br /> "description": "Link to the ARR #support Discord",<br /> "type": "url",<br /> "required": true<br /> },<br /> "ARR_WEBSITE": {<br /> "description": "Link to the ARR Website",<br /> "type": "url",<br /> "required": true<br /> },<br /> "ARR_LATEST_RELEASE": {<br /> "description": "Link to the ARR Download",<br /> "type": "url",<br /> "required": true<br /> },<br /> "VERSION": {<br /> "description": "The current version of each of the ARRs",<br /> "type": "string",<br /> "required": true<br /> },<br /> "MEDIA": {<br /> "description": "What type of media does the ARR use",<br /> "example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",<br /> "type": "string",<br /> "required": true<br /> },<br /> "SEARCHSOURCE": {<br /> "description": "What metadata provider does the ARR use",<br /> "example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",<br /> "type": "string",<br /> "required": true<br /> },<br /> "QUERYSTRING": {},<br /> "ARRNAME2": {<br /> "description": "This string is used for lower cased ARR names for transclusion",<br /> "example": "radarr, sonarr, lidarr, readarr",<br /> "type": "string",<br /> "required": true<br /> }<br /> },<br /> "description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."<br /> }<br /> </templatedata><br /> </noinclude><br /> == Troubleshooting ==<br /> ----<br /> Please note that this information is only for <span style="color:#ff0000">{{{ARRNAME}}} {{{VERSION}}}</span>.<br /> === Asking for Help ===<br /> ----<br /> Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].<br /> <br /> But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono (if not Windows and not .Netcore), version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.<br /> <br /> The more we know, the easier it is to help you.<br /> <br /> == Logging and Log Files ==<br /> <br /> ==== Standard Logs Location ====<br /> The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.<br /> <br /> Note: The Logs Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.<br /> <br /> ==== Update Logs Location ====<br /> The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.<br /> <br /> ==== Sharing Logs ====<br /> The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use a [https://pastebin.com Pastebin]. The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.<br /> <br /> ==== Trace/Debug Logs ====<br /> <br /> You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only effects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.<br /> <br /> If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.<br /> <div style="margin-left: 2em;"><pre><br /> <Config><br /> ...<br /> <LogLevel>debug</LogLevel><br /> ...<br /> </Config><br /> </pre></div><br /> <br /> ==== Clearing Logs ====<br /> <br /> You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)<br /> <br /> ==== Multiple Log Files ====<br /> <br /> {{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is) up to 6 log files total. This log file contains fatal,error,warn and info entries.<br /> <br /> When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present, up to 51 files. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.<br /> <br /> When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present, up to 51 files. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours.<br /> <br /> == Recovering from a Failed Update ==<br /> ----<br /> ==== Purpose ====<br /> We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.<br /> <br /> ==== Determine the issue ====<br /> The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.<br /> <br /> '''Migration Issue'''<br /> <br /> Migration errors won't be identical, but here is an example:<br /> <br /> <code><br /> 14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***<br /> <br /> 14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items<br /> <br /> While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"<br /> <br /> </code><br /> <br /> ==== Resolving the issue ====<br /> In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit], if there are others with the same issue, then rest assured we are working on it.<br /> <br /> ==== Manually upgrading ====<br /> Grab the latest release from [{{{ARR_WEBSITE}}} our website] - if you're running the develop version you can get the latest release [{{{ARR_LATEST_RELEASE}}} HERE]<br /> <br /> Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.<br /> <br /> == Downloads and Importing ==<br /> <br /> Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} needs to be able to communicate with your download client and have access to the files it downloads. There is a large variety of supported download clients and an even ''bigger'' variety of setups. This means that while there are some ''common'' setups, there isn’t one ''right'' setup and everyone’s setup can be a little different.<br /> <br /> Start by using the [[#Logging and Log Files|logging and log files]] article to turn logging up to trace, it is likely you’re going to need to look at them to figure out what is wrong. And if you can’t, anyone you ask for help will need to see them for sure. Remember to get them from the actual log file, put them in a pastebin and show us context around what we need to see. Nobody wants to dig through the whole trace log (it is huge!), but just a line or two is unlikely to help.<br /> <br /> When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.<br /> <br /> === Testing the Download Client ===<br /> <br /> Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.<br /> <br /> === Testing a Download ===<br /> <br /> Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.<br /> <br /> === Testing an Import ===<br /> <br /> Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.<br /> <br /> Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.<br /> <br /> === Common Problems ===<br /> <br /> ==== Can’t see share on Windows ====<br /> <br /> The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.<br /> <br /> ==== Mapped network drives are not reliable ====<br /> <br /> While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.<br /> <br /> ==== Docker and user, group, ownership, permissions and paths ====<br /> <br /> Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.<br /> <br /> ==== Download client clearing items ====<br /> <br /> The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.<br /> <br /> ==== Download folder and library folder not different folders ====<br /> <br /> The download client should download into a temporary-ish folder and {{{ARRNAME}}} should import from that into your Library folder. If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, you may not notice because your media server will see the download client copy. The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.<br /> <br /> ==== Incorrect category ====<br /> <br /> {{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added w/o the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.<br /> <br /> ==== Packed torrents ====<br /> <br /> If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. You can typically search your torrent client’s name and “unpack” to find a solution. There are some other interesting solutions in this space, like [https://github.com/davidnewhall/unpackerr unpackerr] and [https://sourceforge.net/projects/rarfs/ rarfs], but they’re more complicated. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated w/ a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].<br /> <br /> ==== Permissions on the destination ====<br /> <br /> Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.<br /> <br /> ==== Repeated downloads ====<br /> <br /> There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored w/ the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.<br /> <br /> ==== Usenet download misses import ====<br /> <br /> {{{ARRNAME}}} only looks at the 30 most recent downloads in sabnzbd and nzbget, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.<br /> <br /> ==== qBittorrent 4.3.x ====<br /> <br /> This version of qB changed how torrent folder and torrent name relate, previous to this the folder was named after the torrent. Starting in this version, the torrent folder name can be different. This is fixed in v3.<br /> <br /> == Searches Indexers and Trackers ==<br /> <br /> === Turn logging up to trace ===<br /> <br /> The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue. If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.<br /> <br /> === Testing an Indexer or Tracker ===<br /> <br /> When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.<br /> <br /> {{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}<br /> <br /> === Testing a Search ===<br /> {{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}<br /> <br /> [[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]<br /> <br /> [[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]<br /> <br /> {{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}<br /> <br /> Here you can see the ''full'' trace log below<br /> {{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}<br /> <br /> === Common Problems ===<br /> <br /> ==== Wrong categories ====<br /> <br /> Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.<br /> {{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}<br /> ==== Wrong results ====<br /> <br /> Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.<br /> <br /> ==== Certificate validation ====<br /> <br /> You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date. And if you’re using Mono, <code>MONO_TLS_PROVIDER=legacy</code> was a fix from ''years'' ago that should ''not'' be used anymore, so make sure you’re not setting that accidentally.<br /> <br /> ==== Hitting rate limits ====<br /> <br /> If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, Xem and/or your indexers and trackers. Rate limiting and ddos protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy your {{{ARRNAME}}}.<br /> <br /> ==== Using the Jackett /all endpoint ====<br /> <br /> The Jackett <code>/all</code> endpoint is convenient, but that is essentially its only benefit. Everything else is potential problems, so adding each tracker individually is preferred. It allows for fine tuning of categories on a per tracker basis, which can be a problem w/ the <code>/all</code> end point if using the wrong category causes errors on some. In {{{ARRNAME}}}, each indexer/tracker is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.<br /> <br /> === Errors ===<br /> <br /> These are some of the common errors you may see when adding an indexer<br /> <br /> ==== The underlying connection was closed: An unexpected error occurred on a send. ====<br /> <br /> This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).<br /> <br /> ==== Error getting response stream (Write: The authentication or decryption has failed.): SendFailure ====<br /> <br /> This is caused by the indexer using a new certificate authority that is not trusted by mono 2.10. The solution is to upgrade to mono 3.x, on Ubuntu this can be done via this method: http://stackoverflow.com/a/13384233/882971 We recommend upgrading to mono 3.x to fix a number of bugs and add support for .net 4.5 features.<br /> <br /> ==== The request timed out ====<br /> <br /> {{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log: <br /> <pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&amp;apikey=(removed) —&gt; System.Net.WebException: The request timed out</pre><br /> <br /> And you can see the following in the trace logfile:<br /> <pre>&lt;DATE&amp;TIME&gt;|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre><br /> <br /> You might fix it by installing libcurl3. On Ubuntu/Debian use; <br /> <pre>apt install libcurl3</pre></div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2707 Docker ARM Synology 2020-12-11T21:43:56Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Summary==<br /> <br /> The instructions below will:<br /> # Place the docker binaries in <code>/usr/local/bin/</code><br /> # Create a docker config file <code>/usr/local/etc/docker/docker.json</code><br /> # Configure docker to save its data to <code>/volume1/docker/var</code><br /> # Create a script to start docker on boot at <code>/usr/local/etc/rc.d/docker.sh</code><br /> # Create a <code>docker</code> group<br /> # Place a docker-compose script in <code>/usr/local/bin/</code><br /> <br /> ==Installation==<br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up a docker GUI==<br /> If you want a GUI you can run Portainer using the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in a file called <code>docker-compose.yml</code> in an otherwise empty directory. Run:<br /> docker-compose up -d<br /> Visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> ==Setting up Sonarr/Radarr/Lidarr/Readarr==<br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and '''remember caveat 2 above.'''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2706 Docker ARM Synology 2020-12-11T20:06:58Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Summary==<br /> <br /> The instructions below will:<br /> # Place the docker binaries in <code>/usr/local/bin/</code><br /> # Create a docker config file <code>/usr/local/etc/docker/docker.json</code><br /> # Configure docker to save its data to <code>/volume1/docker/var</code><br /> # Create a script to start docker on boot at <code>/usr/local/etc/rc.d/docker.sh</code><br /> # Create a <code>docker</code> group<br /> # Place a docker-compose script in <code>/usr/local/bin/</code><br /> <br /> ==Installation==<br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up a docker GUID==<br /> If you want a GUI you can run Portainer using the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in a file called <code>docker-compose.yml</code> in an otherwise empty directory. Run:<br /> docker-compose up -d<br /> Visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> ==Setting up Sonarr/Radarr/Lidarr/Readarr==<br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and '''remember caveat 2 above.'''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2705 Docker ARM Synology 2020-12-11T20:06:31Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> The instructions below will <br /> # Place the docker binaries in <code>/usr/local/bin/</code><br /> # Create a docker config file <code>/usr/local/etc/docker/docker.json</code><br /> # Configure docker to save its data to <code>/volume1/docker/var</code><br /> # Create a script to start docker on boot at <code>/usr/local/etc/rc.d/docker.sh</code><br /> # Create a <code>docker</code> group<br /> # Place a docker-compose script in <code>/usr/local/bin/</code><br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up a docker GUID==<br /> If you want a GUI you can run Portainer using the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in a file called <code>docker-compose.yml</code> in an otherwise empty directory. Run:<br /> docker-compose up -d<br /> Visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> ==Setting up Sonarr/Radarr/Lidarr/Readarr==<br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and '''remember caveat 2 above.'''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2704 Docker ARM Synology 2020-12-11T20:03:12Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up a docker GUID==<br /> If you want a GUI you can run Portainer using the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in a file called <code>docker-compose.yml</code> in an otherwise empty directory. Run:<br /> docker-compose up -d<br /> Visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> ==Setting up Sonarr/Radarr/Lidarr/Readarr==<br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and '''remember caveat 2 above.'''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2703 Docker ARM Synology 2020-12-11T20:00:09Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up a docker GUID==<br /> If you want a GUI you can run Portainer using the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> ==Setting up Sonarr/Radarr/Lidarr/Readarr==<br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and '''remember caveat 2 above.'''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2702 Docker ARM Synology 2020-12-11T19:59:04Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and '''remember caveat 2 above.'''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2701 Docker ARM Synology 2020-12-11T19:58:52Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).<br /> <br /> For guidance setting up Sonarr/Radarr/Lidarr/Readarr, see the [[Docker Guide]], and ''remember caveat 2 above.''</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2700 Docker ARM Synology 2020-12-11T19:57:38Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new <code>docker</code> group using the Synology GUI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have functioning <code>docker</code> and <code>docker-compose</code> commands, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2699 Docker ARM Synology 2020-12-11T19:56:37Z

<p>Ta264: </p> <hr /> <div>==Introduction==<br /> Synology only offer a docker package on their <code>x64</code> based NAS. Using this method to install docker on an <code>aarch64</code> NAS is totally unsupported/untested and totally at your own risk. It is entirely possible it will destroy your NAS.<br /> <br /> ==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new 'docker' group using the synology UI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have a functioning <code>docker</code> and <code>docker-compose</code>, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use <code>--network=host</code> (or <code>network: host</code> in compose) and everything will be directly accessible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2698 Docker ARM Synology 2020-12-11T19:53:26Z

<p>Ta264: </p> <hr /> <div>==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new 'docker' group using the synology UI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have a functioning <code>docker</code> and <code>docker-compose</code>, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker).<br /> # Again, due to Synology constraints, all containers need to use `--network=host` (or `network: host` in compose) and everything will be directly accesible from the host. There are no port maps.<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2697 Docker ARM Synology 2020-12-11T19:52:49Z

<p>Ta264: </p> <hr /> <div>==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new 'docker' group using the synology UI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have a functioning <code>docker</code> and <code>docker-compose</code>, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker)<br /> # Again, due to Synology constraints, all containers need to use `--network=host` (or `network: host` in compose) and everything will be directly accesible from the host. There are no port maps<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup (where <code>ip</code> is the IP address of your synology).</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2696 Docker ARM Synology 2020-12-11T19:52:17Z

<p>Ta264: </p> <hr /> <div>==Installation==<br /> <br /> Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new 'docker' group using the synology UI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have a functioning <code>docker</code> and <code>docker-compose</code>, which should work when logged in as your normal user.<br /> <br /> ==Caveats==<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker)<br /> # Again, due to Synology constraints, all containers need to use `--network=host` (or `network: host` in compose) and everything will be directly accesible from the host. There are no port maps<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> ==Setting up Portainer==<br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre><br /> <br /> Place this in an empty directory and call it <code>docker-compose.yml</code>. Run:<br /> docker-compose up -d<br /> And visit <code>http://ip:9000</code> to complete setup.</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2695 Docker ARM Synology 2020-12-11T19:47:44Z

<p>Ta264: </p> <hr /> <div>Log in as <code>root</code> to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new 'docker' group using the synology UI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have a functioning <code>docker</code> and <code>docker-compose</code>, which should work when logged in as your normal user.<br /> <br /> Some caveats:<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker)<br /> # Again, due to Synology constraints, all containers need to use `--network=host` (or `network: host` in compose) and everything will be directly accesible from the host. There are no port maps<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre></div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2694 Docker ARM Synology 2020-12-11T19:43:32Z

<p>Ta264: </p> <hr /> <div>Log in as `root` to your synology. Execute the following command:<br /> <br /> curl https://gist.githubusercontent.com/ta264/2b7fb6e6466b109b9bf9b0a1d91ebedc/raw/7b11f25c3dce181faa5206aed8051f176cc4e406/get-docker.sh | sh<br /> <br /> If all goes well you should see the message:<br /> <pre>Done. Please add your user to the docker group in the Synology GUI and reboot your NAS.</pre><br /> <br /> Do as it says:<br /> # Add your user to the new 'docker' group using the synology UI<br /> # '''Reboot.''' <br /> <br /> Hopefully you have a functioning `docker` and `docker-compose`, which should work when logged in as your normal user.<br /> <br /> Some caveats:<br /> # It seems most ARM Synology don't support seccomp, so the docker container has unfettered access to your system (even more so than with a regular docker)<br /> # Again, due to Synology constraints, all containers need to use `--network=host` (or `network: host` in compose) and everything will be directly accesible from the host. There are no port maps<br /> # Obviously you can only run aarch64 images, but most hotio and linuxserver images offer an aarch64 version.<br /> <br /> If you want a GUI you can use the following example compose:<br /> <br /> <pre><br /> version: '2'<br /> <br /> services:<br /> portainer:<br /> image: portainer/portainer<br /> restart: unless-stopped<br /> network_mode: host<br /> volumes:<br /> - /var/run/docker.sock:/var/run/docker.sock<br /> - portainer_data:/data<br /> <br /> volumes:<br /> portainer_data:<br /> </pre></div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2688 Docker ARM Synology 2020-12-11T18:37:08Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group, replacing MYUSERNAME with the username you use to log in with SSH<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Install docker compose:<br /> <br /> <pre><br /> curl -L --fail https://gist.githubusercontent.com/ta264/af20c367aafa63795c3104d4b0c8b148/raw/4f6d257c026596cfce1c9052d9ac426a50e9f205/run.sh -o /usr/local/bin/docker-compose<br /> chmod +x /usr/local/bin/docker-compose<br /> </pre><br /> <br /> Reboot. <br /> <br /> Hopefully you have a functioning `docker` and `docker-compose`<br /> <br /> You can start portainer with:<br /> docker run --network=host -v "/var/run/docker.sock:/var/run/docker.sock" portainer/portainer-ce:linux-arm64<br /> <br /> Which will start portainer on port 9000 on the host.</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2687 Docker ARM Synology 2020-12-11T17:33:57Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group, replacing MYUSERNAME with the username you use to log in with SSH<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot. <br /> <br /> You can try to install docker compose:<br /> <br /> <pre><br /> sudo curl -L --fail https://raw.githubusercontent.com/linuxserver/docker-docker-compose/master/run.sh -o /usr/local/bin/docker-compose<br /> sudo chmod +x /usr/local/bin/docker-compose<br /> </pre><br /> <br /> But in our test this failed with <br /> <pre><br /> Status: Downloaded newer image for ghcr.io/linuxserver/docker-compose:latest<br /> docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: open /dev/ptmx: no such file or directory: unknown.<br /> </pre><br /> <br /> You can start portainer with:<br /> docker run --network=host -v "/var/run/docker.sock:/var/run/docker.sock" portainer/portainer-ce:linux-arm64<br /> <br /> Which will start portainer on port 9000 on the host.</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2686 Docker ARM Synology 2020-12-11T17:20:38Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group, replacing MYUSERNAME with the username you use to log in with SSH<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot. <br /> <br /> You can try to install docker compose:<br /> <br /> <pre><br /> sudo curl -L --fail https://raw.githubusercontent.com/linuxserver/docker-docker-compose/master/run.sh -o /usr/local/bin/docker-compose<br /> sudo chmod +x /usr/local/bin/docker-compose<br /> </pre><br /> <br /> But in our test this failed with <br /> <pre><br /> Status: Downloaded newer image for ghcr.io/linuxserver/docker-compose:latest<br /> docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: open /dev/ptmx: no such file or directory: unknown.<br /> </pre></div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2685 Docker ARM Synology 2020-12-11T16:46:10Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group, replacing MYUSERNAME with the username you use to log in with SSH<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot. Then install docker compose:<br /> <br /> <pre><br /> sudo curl -L --fail https://raw.githubusercontent.com/linuxserver/docker-docker-compose/master/run.sh -o /usr/local/bin/docker-compose<br /> sudo chmod +x /usr/local/bin/docker-compose<br /> </pre></div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2683 Docker ARM Synology 2020-12-11T15:52:55Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group, replacing MYUSERNAME with the username you use to log in with SSH<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot. Then install docker compose:<br /> <br /> <pre><br /> sudo curl -L --fail https://github.com/docker/compose/releases/download/1.27.4/run.sh -o /usr/local/bin/docker-compose<br /> sudo chmod +x /usr/local/bin/docker-compose<br /> </pre></div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2682 Docker ARM Synology 2020-12-11T15:33:28Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group, replacing MYUSERNAME with the username you use to log in with SSH<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2681 Docker ARM Synology 2020-12-11T15:32:59Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group<br /> <br /> synogroup --add docker root MYUSERNAME<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2680 Docker ARM Synology 2020-12-11T15:25:40Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> <pre><br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> </pre><br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group<br /> <br /> synogroup --add docker root<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2679 Docker ARM Synology 2020-12-11T15:17:56Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Create the docker group<br /> <br /> synogroup --add docker root<br /> <br /> Start it!<br /> <br /> /usr/local/etc/rc.d/docker.sh start<br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2678 Docker ARM Synology 2020-12-11T14:51:52Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT > /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' > /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2677 Docker ARM Synology 2020-12-11T14:47:55Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<'EOT' >> /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2676 Docker ARM Synology 2020-12-11T14:43:01Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2675 Docker ARM Synology 2020-12-11T14:41:19Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/usr/local/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> <br /> chmod 755 /usr/local/etc/rc.d/docker.sh<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2674 Docker ARM Synology 2020-12-11T14:40:52Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker.sh<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/usr/local/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2673 Docker ARM Synology 2020-12-11T14:36:20Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/usr/local/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2672 Docker ARM Synology 2020-12-11T14:36:06Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/usr/local/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> PATH=/opt/sbin:/opt/bin:/opt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> EOT<br /> </pre><br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2671 Docker ARM Synology 2020-12-11T14:34:53Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/docker<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/usr/local/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> PATH=/opt/sbin:/opt/bin:/opt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2670 Docker ARM Synology 2020-12-11T14:27:56Z

<p>Ta264: </p> <hr /> <div>Log in as root to your synology. Download and extract the docker binaries by running:<br /> <br /> curl https://download.docker.com/linux/static/stable/aarch64/docker-20.10.0.tgz | tar -xz -C /usr/local/bin --strip-components=1<br /> <br /> Create somewhere for the docker files to live:<br /> <br /> mkdir -p /volume1/@Docker/lib <br /> mkdir /docker <br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> Configure docker:<br /> <pre><br /> mkdir -p /usr/local/etc/<br /> cat <<EOT >> /usr/local/etc/docker/docker.json<br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }<br /> EOT<br /> </pre><br /> <br /> Enable docker to start on boot:<br /> <br /> <pre><br /> cat <<EOT >> /usr/local/etc/rc.d/docker<br /> #!/bin/sh<br /> # Start docker daemon<br /> <br /> NAME=dockerd<br /> PIDFILE=/usr/local/var/run/$NAME.pid<br /> DAEMON_ARGS="--config-file=/usr/local/etc/docker/docker.json --pidfile=$PIDFILE"<br /> PATH=/opt/sbin:/opt/bin:/opt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin<br /> <br /> case "$1" in<br /> start)<br /> echo "Starting docker daemon"<br /> mount -o bind "/volume1/@Docker/lib" /docker<br /> /usr/local/bin/dockerd $DAEMON_ARGS &<br /> ;;<br /> stop)<br /> echo "Stopping docker daemon"<br /> kill $(cat $PIDFILE)<br /> ;;<br /> *)<br /> echo "Usage: "$1" {start|stop}"<br /> exit 1<br /> esac<br /> exit 0<br /> <br /> Reboot</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2669 Docker ARM Synology 2020-12-11T12:09:17Z

<p>Ta264: </p> <hr /> <div>Download https://download.docker.com/linux/static/stable/aarch64/<br /> <br /> tar xzvf /path/to/.tar.gz<br /> sudo cp docker/* /usr/bin/<br /> <br /> sudo mkdir -p /volume1/@Docker/lib <br /> sudo mkdir /docker <br /> sudo mount -o bind "/volume1/@Docker/lib" /docker<br /> <br /> sudo mkdir /etc/docker<br /> sudo vi /etc/docker/docker.json<br /> <br /> {<br /> "storage-driver": "vfs",<br /> "iptables": false,<br /> "bridge": "none",<br /> "data-root": "/docker"<br /> }</div>

Ta264 https://wikiold.servarr.com/index.php?title=Docker_ARM_Synology&diff=2668 Docker ARM Synology 2020-12-11T11:54:04Z

<p>Ta264: Created page with "Download https://download.docker.com/linux/static/stable/aarch64/"</p> <hr /> <div>Download https://download.docker.com/linux/static/stable/aarch64/</div>

Ta264 https://wikiold.servarr.com/index.php?title=WikiMap&diff=2667 WikiMap 2020-12-11T11:53:23Z

<p>Ta264: </p> <hr /> <div>Please use https://github.com/Servarr/Wiki to track issues<br /> Please use this page for easy access to templates<br /> <br /> This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.<br /> <br /> == Stand Alone Templates ==<br /> <br /> # [[Template:Appdata Directory]]<br /> # [[Template:Installation]]<br /> # [[Template:Troubleshooting]]<br /> <br /> == Miscellaneous ==<br /> # [[Sandbox]] <- Test code and do any testing here before sending it to live<br /> # [[Useful Tools]]<br /> # [[Cloud Setup|Rclone/Mergerfs/Gdrive setup & links]]<br /> # [[Docker Guide]]<br /> # [[Definitions]]<br /> # [[Discord-Notifier-unRAID-Plex]]<br /> # [[Discord-Notifier-unRAID-Network]]<br /> # [[Clear Cache Cookies and Local Storage]]<br /> # [[Troubleshooting Misc]]<br /> # [[Appdata Directory Misc]]<br /> # [[Installation Misc]]<br /> # [[Docker on arm synology]]<br /> <br /> == Stand Alone Pages ==<br /> * [[Radarr]]<br /> <br /> * [[Sonarr]]<br /> <br /> * [[Lidarr]]<br /> <br /> * [[Readarr]]<br /> <br /> == API Documentation ==<br /> * [https://radarr.video/docs/api/ Radarr]<br /> <br /> * Sonarr<br /> <br /> * Lidarr<br /> <br /> * Readarr<br /> <br /> == *ARR Pages ==<br /> <section begin=radarr_wiki_pages /><br /> *[[Radarr]]<br /> **[[Radarr Installation]]<br /> **[[Radarr Quick Start Guide]]<br /> **[[Radarr Library|Radarr Library (Movies)]]<br /> **[[Radarr Calendar]]<br /> **[[Radarr Activity]]<br /> **[[Radarr Settings]]<br /> **[[Radarr System]]<br /> **[[Radarr Troubleshooting]]<br /> **[[Radarr FAQ]]<br /> **[[Radarr Tips and Tricks]]<section end=radarr_wiki_pages /><section begin=sonarr_wiki_pages /><br /> *[[Sonarr]]<br /> **[[Sonarr Installation]]<br /> **[[Sonarr Quick Start Guide]]<br /> **[[Sonarr Library|Sonarr Library (Series)]]<br /> **[[Sonarr Calendar]]<br /> **[[Sonarr Activity]]<br /> **[[Sonarr Settings]]<br /> **[[Sonarr System]]<br /> **[[Sonarr Troubleshooting]]<br /> **[[Sonarr FAQ]]<br /> **[[Sonarr Tips and Tricks]]<section end=sonarr_wiki_pages /><section begin=lidarr_wiki_pages /><br /> *[[Lidarr]]<br /> **[[Lidarr Installation]]<br /> **[[Lidarr Quick Start Guide]]<br /> **[[Lidarr Library|Lidarr Library (Artist)]]<br /> **[[Lidarr Calendar]]<br /> **[[Lidarr Activity]]<br /> **[[Lidarr Settings]]<br /> **[[Lidarr System]]<br /> **[[Lidarr Troubleshooting]]<br /> **[[Lidarr FAQ]]<br /> **[[Lidarr Tips and Tricks]]<section end=lidarr_wiki_pages /><section begin=readarr_wiki_pages /><br /> *[[Readarr]]<br /> **[[Readarr Installation]]<br /> **[[Readarr Quick Start Guide]]<br /> **[[Readarr Library|Readarr Library]]<br /> **[[Readarr Calendar]]<br /> **[[Readarr Activity]]<br /> **[[Readarr Settings]]<br /> **[[Readarr System]]<br /> **[[Readarr Troubleshooting]]<br /> **[[Readarr FAQ]]<br /> **[[Readarr Tips and Tricks]]<section end=readarr_wiki_pages /><br /> <br /> == * ARR UI Pages ==<br /> Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.<br /> === Movies/Series/Library ===<br /> # [[Library]]<br /> # [[Library Add New]]<br /> # [[Library Import]]<br /> # [[Library Discover]] <-- Radarr<br /> # [[Library Mass Editor]] <-- Sonarr/Lidarr<br /> # [[Library Season Pass]] <-- Sonarr<br /> # [[Library Album Studio]] <-- Lidarr<br /> # [[Library Bookshelf]] <-- Readarr<br /> # [[Library Unmapped Files]] <-- Lidarr/Readarr<br /> <br /> === Calendar ===<br /> # [[Calendar]]<br /> <br /> === Activity ===<br /> # [[Activity Queue]]<br /> # [[Activity History]]<br /> # [[Activity Blacklist]]<br /> <br /> === Wanted ===<br /> # [[Wanted]]<br /> # [[Wanted Missing]]<br /> # [[Wanted Cutoff Unmet]]<br /> <br /> === Settings ===<br /> # [[Settings Media Management]]<br /> # [[Settings Profiles]]<br /> # [[Settings Quality]]<br /> # [[Settings Custom Formats]]<br /> # [[Settings Indexers]]<br /> # [[Settings Download Clients]]<br /> # [[Settings Lists]]<br /> # [[Settings Connect]]<br /> # [[Settings Metadata]]<br /> # [[Settings Tags]]<br /> # [[Settings General]]<br /> # [[Settings UI]]<br /> === System ===<br /> # [[System status|System Status]]<br /> # [[System tasks|System Tasks]]<br /> # [[System backup|System Backup]]<br /> # [[System updates|System Updates]]<br /> # [[System events|System Events]]<br /> # [[System log files|System Log Files]]</div>

Ta264 https://wikiold.servarr.com/index.php?title=System_status&diff=2478 System status 2020-11-30T16:33:40Z

<p>Ta264: /* Radarr */</p> <hr /> <div>== System ==<br /> === Health ===<br /> ==== Overview ====<br /> ====== Radarr ======<br /> <section begin=radarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=radarr_system_status_health_overview /><br /> ====== Sonarr ======<br /> <section begin=sonarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=sonarr_system_status_health_overview /><br /> ====== Lidarr ======<br /> <section begin=lidarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=lidarr_system_status_health_overview /><br /> ====== Readarr ======<br /> <section begin=readarr_system_status_health_overview /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> <section end=readarr_system_status_health_overview /><br /> ==== System Warnings ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_system_warnings /><br /> * <span id="update-to-net-core-version">'''[[#update-to-net-core-version|Update to .NET Core version]]'''</span><br /> ** Newer versions of Radarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.<br /> ** Fixing Docker installs<br /> *** Re-pull your container<br /> ** Fixing Standalone installs<br /> <br /> *** This should only happen on linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br /> **** [https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64] <br /> **** [https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64] <br /> **** [https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br /> *** <span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br /> *** '''Delete your existing binaries' (contents or folder of /opt/Radarr)'' and replace with the contents of the <code>.tar.gz</code> you just downloaded. <br /> *** <span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br /> **** Update your startup script to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br /> *** If Radarr doesn’t start make sure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br /> * <span id="Mono_version_is_less_than_3_10_upgrade_for_improved_stability">'''[[#Mono_version_is_less_than_3_10_upgrade_for_improved_stability|Mono version is less than 3.10, upgrade for improved stability]]'''</span><br /> ** Radarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.<br /><br /> ** Mono version 4.x and higher are also available and provides a better experience on certain platforms.<br /> ** See "Update to .NET Core version above"<br /> * <span id="New_update_is_available">'''[[#New_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> * <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#Cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.<br /> * <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''[[#Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> ** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /> ** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br /> ** This means Radarr will be unable to update itself without risking data-loss.<br /> ** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br /> * <span id="Branch_is_for_a_previous_version">'''[[#Branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br /> ** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.<br /> ** '''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within radarr’s settings), once we push a build to Github it will show up on “develop” release channel.<br /> * <span id="Could_not_connect_to_signalR">'''[[#Could_not_connect_to_signalR|Could not connect to signalR]]'''</span><br /> ** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.<br /> ** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr: <br /> *::<code>proxy_http_version 1.1;</code><br /> *::<code>proxy_set_header Upgrade $http_upgrade;</code><br /> *::<code>proxy_set_header Connection $http_connection;</code><br /> ** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br /> ** See https://github.com/aspnet/AspNetCore/issues/17081<br /> ** For apache reverse proxy you need to add to the configuration:<br /> *::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br /> *::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br /> *::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br /> <section end=radarr_system_status_health_system_warnings /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_system_warnings /><br /> This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.<br /> * '''Currently installed .Net Framework is old and unsupported'''<br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> * <span id="Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended">'''[[#Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.<br /> * <span id="Currently_installed_mono_version_is_old_and_unsupported">'''[[#Currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br /> ** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform.<br /><br /> ** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br /> ** The upgrade procedure for Mono varies per platform.<br /> * <span id="Currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#Currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br /> ** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.<br /> ** The upgrade procedure for Mono varies per platform.<br /> * <span id="New_update_is_available">'''[[#New_update_is_available|New update is available]]'''</span><br /> ** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -&gt; Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.<br /> ** ''(This warning will not appear if your current version is less than 14 days old)''<br /> * <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#Cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br /> ** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.<br /> * <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''[[#Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br /> **Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br /> ** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br /> ** This means Sonarr will be unable to update itself without risking data-loss.<br /> ** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br /> <section end=sonarr_system_status_health_system_warnings /><br /> <br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_system_warnings /><br /> Text<br /> <section end=lidarr_system_status_health_system_warnings /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_system_warnings /><br /> Text<br /> <section end=readarr_system_status_health_system_warnings /><br /> <br /> <br /> ==== Download Clients ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_download_clients /><br /> * <span id="no_download_client_is_available>'''[[#no_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -&gt; Download Client.<br /> ** Unable to communicate with download client<br /> ** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> * <span id="Download_clients_are_unavailable_due_to_failure">'''[[#Download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Radarr to prevent the errors.<br /> * <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br /> ** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <section end=radarr_system_status_health_download_clients /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_download_clients /><br /> * <span id="No_download_client_is_available">'''[[#No_download_client_is_available|No download client is available]]'''</span><br /> ** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -&gt; Download Client.<br /> ** Unable to communicate with download client ====<br /> ** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.<br /> * <span id="Download_clients_are_unavailable_due_to_failure">'''[[#Download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br /> ** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.<br /> ** You should inspect System-&gt;Logs to see what the reason is for the failures.<br /> ** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br /> * <span id="Enable_Completed_Download_Handling_or_configure_Drone_Factory">'''[[#Enable_Completed_Download_Handling_or_configure_Drone_Factory|Enable Completed Download Handling or configure Drone Factory]]'''</span><br /> ** Sonarr requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br /> ** ''(Completed Download Handling is enabled by default for new users.)''<br /> <section end=sonarr_system_status_health_download_clients /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_download_clients /><br /> Text<br /> <section end=lidarr_system_status_health_download_clients /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_download_clients /><br /> Text<br /> <section end=readarr_system_status_health_download_clients /><br /> <br /> ==== Completed/Failed Download Handling ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_complete_failed_download_handling /><br /> * <span id="Completed_Download_Handling_is_disabled">'''[[#Completed_Download_Handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It’s recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.<br /> ** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.<br /> ** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> ** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=radarr_system_status_health_complete_failed_download_handling /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_complete_failed_download_handling /><br /> * <span id="Completed_Download_Handling_is_disabled">'''[[#Completed_Download_Handling_is_disabled|Completed Download Handling is disabled]]'''</span><br /> ** ''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''<br /> ** It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.<br /> ** If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.<br /> ** If you wish to enable Completed Download Handling you should verify the following:<br /> *** '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.<br /> *** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.<br /> *** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)<br /><br /> ** You should reconfigure Sonarr to use a different Drone Factory Folder or disable it altogether.<br /><br /> Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.<br /> ** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.<br /> <section end=sonarr_system_status_health_complete_failed_download_handling /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_complete_failed_download_handling /><br /> Text<br /> <section end=lidarr_system_status_health_complete_failed_download_handling /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_complete_failed_download_handling /><br /> Text<br /> <section end=readarr_system_status_health_complete_failed_download_handling /><br /> <br /> <br /> ==== Indexers ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_indexers /><br /> * <span id="No_indexers_are_enabled">'''[[#No_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br /> * <span id="Enabled_indexers_do_not_support_searching">'''[[#Enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br /> ** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="Indexers_are_unavailable_due_to_failures">'''[[#Indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).<br /> ** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> ** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=radarr_system_status_health_indexers /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_indexers /><br /> * <span id="No_indexers_are_enabled">'''[[#No_indexers_are_enabled|No indexers are enabled]]'''</span><br /> ** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br /> * <span id="Enabled_indexers_do_not_support_searching">'''[[#Enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br /> ** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.<br /> * <span id="Indexers_are_unavailable_due_to_failures">'''[[#Indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br /> ** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).<br /><br /> ** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.<br /> ** You can prevent the warning by disabling the affected indexer.<br /> **Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.<br /> <section end=sonarr_system_status_health_indexers /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_indexers /><br /> Text<br /> <section end=lidarr_system_status_health_indexers /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_indexers /><br /> Text<br /> <section end=readarr_system_status_health_indexers /><br /> <br /> ==== Folders ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_folders /><br /> * <span id="Missing_root_folder">'''[[#Missing_root_folder|Missing root folder]]'''</span><br /> ** This message may appear if a previous root folder is no longer used. To remove old root folders:<br /> *** Begin adding a new Movie* by searching for a name, but do not submit<br /> *** In the 'Path' dropdown, select 'Add a different path'<br /> *** Click the cross at the end of a row to remove the unused path<br /> ** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Radarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br /> ** The message will continue to appear until all movies have their root folder updated to the new root folder. To change the root folder for other movies, visit the movies editor.<br /> *** NB: I thought Radarr was for Movies and not Series<br /> <section end=radarr_system_status_health_folders /><br /> <br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_folders /><br /> * <span id="Missing root folder">'''[[#Missing root folder|Missing root folder]]'''</span><br /> ** This message may appear if a previous root folder is no longer used. To remove old root folders:<br /> **# Begin adding a new Series by searching for a name, but do not submit<br /> **# In the 'Path' dropdown, select 'Add a different path'<br /> **# Click the cross at the end of a row to remove the unused path<br /> ** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Sonarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br /> ** The message will continue to appear until all series have their root folder updated to the new root folder. To change the root folder for other series, visit the series editor.<br /> <section end=sonarr_system_status_health_folders /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_folders /><br /> Text<br /> <section end=lidarr_system_status_health_folders /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_folders /><br /> Text<br /> <section end=readarr_system_status_health_folders /><br /> <br /> ==== Media ====<br /> ===== Radarr =====<br /> <section begin=radarr_system_status_health_media /><br /> * <span id="Movie was removed from TMDb">'''[[#Movie was removed from TMDb|Movie was removed from TMDb]]'''</span><br /> ** The specific movie is linked to a TMDbId that was deleted from TMDb. This may mean that the movie was either removed from the DB, was a duplicate, or was re-assigned a new ID for some reason. Deleted movies will not receive any info updates and should be corrected by the user to ensure continued functionality.<br /><br /> ** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu<br /> <section end=radarr_system_status_health_media /><br /> ===== Sonarr =====<br /> <section begin=sonarr_system_status_health_media /><br /> * <span id="Series_Removed_from_TheTVDB">'''[[#Series_Removed_from_TheTVDB|Series Removed from TheTVDB]]'''</span><br /> ** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.<br /> <section end=sonarr_system_status_health_media /><br /> ===== Lidarr =====<br /> <section begin=lidarr_system_status_health_media /><br /> Text<br /> <section end=lidarr_system_status_health_media /><br /> ===== Readarr =====<br /> <section begin=readarr_system_status_health_media /><br /> Text<br /> <section end=readarr_system_status_health_media /><br /> <br /> === Disk Space ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_disk_space /><br /> * This section will show you available disk space<br /> ** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br /> <section end=radarr_system_status_disk_space /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_disk_space /><br /> Text<br /> <section end=sonarr_system_status_disk_space /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_disk_space /><br /> Text<br /> <section end=lidarr_system_status_disk_space /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_disk_space /><br /> Text<br /> <section end=readarr_system_status_disk_space /><br /> <br /> === About ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_about /><br /> This will tell you about your current install of Radarr<br /> <section end=radarr_system_status_about /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_about /><br /> Text<br /> <section end=sonarr_system_status_about /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_about /><br /> Text<br /> <section end=lidarr_system_status_about /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_about /><br /> Text<br /> <section end=readarr_system_status_about /><br /> <br /> === More Info ===<br /> ==== Radarr ====<br /> <section begin=radarr_system_status_more_info /><br /> * Home page: [https://radarr.video Radarr's home page]<br /> * Discord: [https://discord.gg/r5wJPt9 Join our discord]<br /> * Wiki: [https://wiki.servarr.com You're here already]<br /> * Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br /> * Source: [https://github.com/Radarr/Radarr Github]<br /> * Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br /> <section end=radarr_system_status_more_info /><br /> <br /> ==== Sonarr ====<br /> <section begin=sonarr_system_status_more_info /><br /> Text<br /> <section end=sonarr_system_status_more_info /><br /> ==== Lidarr ====<br /> <section begin=lidarr_system_status_more_info /><br /> Text<br /> <section end=lidarr_system_status_more_info /><br /> ==== Readarr ====<br /> <section begin=readarr_system_status_more_info /><br /> Text<br /> <section end=readarr_system_status_more_info /><br /> <br /> === Templates ===</div>

Ta264 https://wikiold.servarr.com/index.php?title=Readarr&diff=1319 Readarr 2020-09-14T09:03:02Z

<p>Ta264: </p> <hr /> <div>Readarr is a ebook (and maybe eventually magazine/audiobook) collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new books from your favorite authors and will grab, sort and rename them<br /> <br /> {| class="wikitable" style="width:70%; text-align:center; margin:auto; background-color:#dd0b1f;"<br /> |-<br /> ! WARNING<br /> |-<br /> |Readarr is still in a Pre-Alpha state and is generally still in a work in progress. Features may be broken, incomplete, or cause spontaneous combustion.<br><p style="font-size 16px;"> '''You have been WARNED!'''</p><br /> |}<br /> <br /> <br /> <br /> == Links ==<br /> *[https://readarr.com/ Readarr Website]<br /> *[https://opencollective.com/Readarr Readarr Donations]<br /> *[https://github.com/Readarr/Readarr Readarr Github]<br /> === Wiki Links===<br /> *[[Readarr]]<br /> *[[Readarr Installation]]<br /> *[[Readarr Library|Readarr Library]]<br /> *[[Readarr Calendar]]<br /> *[[Readarr Activity]]<br /> *[[Readarr Settings]]<br /> *[[Readarr System]]<br /> *[[Readarr Troubleshooting]]<br /> *[[Readarr FAQ]]<br /> *[[Readarr Tips and Tricks]]</div>

Ta264 https://wikiold.servarr.com/index.php?title=Readarr&diff=1318 Readarr 2020-09-14T09:02:46Z

<p>Ta264: </p> <hr /> <div>Readarr is a ebook (and maybe eventually magazine/audiobook) collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new books from your favorite authors and will grab, sort and rename them<br /> <br /> {| class="wikitable" style="width:70%; text-align:center; margin:auto; background-color:#dd0b1f;"<br /> |-<br /> ! WARNING<br /> |-<br /> |Readarr is still in a Pre-Alpha state and is generally still in a work in progress. Features may be broken, incomplete, or cause spontaneous combustion.<br><p style="font-size 16px;"> '''You have been WARNED!'''</p><br /> |}<br /> <br /> <br /> <br /> == Links ==<br /> *[https://readarr.com/ Readarr Website]<br /> *[https://opencollective.com/Readarr Readarr Donations]<br /> *[https://github.com/Readarr/Readarr Readarr Github]<br /> === Wiki Links===<br /> *[[Readarr]]<br /> *[[Readarr Installation]]<br /> *[[Readarr Library|Readarr Library]]<br /> *[[Readarr Calendar]]<br /> *[[Readarr Activity]]<br /> *[[Readarr Settings]]<br /> *[[Readarr System]]<br /> *[[Readarr Troubleshooting]]<br /> *[[Readarr FAQ]]<br /> *[[Readarr Tips and Tricks]]<br /> <br /> Test</div>

Ta264 https://wikiold.servarr.com/index.php?title=Radarr_Tips_and_Tricks&diff=884 Radarr Tips and Tricks 2020-09-05T19:59:47Z

<p>Ta264: /* Trash's Custom Formats */</p> <hr /> <div>=== [https://github.com/TRaSH-/Tutorials-FAQ/blob/master/RadarrV3/Collection-of-Custom-Formats-for-RadarrV3.md Trash's Custom Formats] ===<br /> {{#github:RadarrV3/Collection-of-Custom-Formats-for-RadarrV3.md|TRaSH-/Tutorials-FAQ|master}}</div>

Ta264