System status - Revision history

Bakerboy448: root folder updates....

2021-05-14T00:32:01Z

root folder updates....

Bakerboy448: /* Radarr */

2021-05-12T20:15:03Z

Radarr

Bakerboy448 at 04:54, 9 May 2021

2021-05-09T04:54:54Z

TRaSH: /* Radarr */

2021-05-08T21:21:36Z

Radarr

Bakerboy448: /* Radarr */

2021-05-08T01:20:42Z

Radarr

Bakerboy448: /* System Warnings */

2021-05-06T23:25:10Z

System Warnings

Bakerboy448: /* More Info */

2021-05-04T23:02:21Z

More Info

Bakerboy448: /* About */

2021-05-04T23:02:11Z

About

Bakerboy448: /* Download Clients */

2021-05-04T23:00:55Z

Download Clients

Bakerboy448: /* Lidarr */

2021-05-04T23:00:03Z

Lidarr

@@ Line 394: / Line 394: @@
 * <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
-** You're downloading directly into your root folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
+** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
 * <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
@@ Line 430: / Line 430: @@
 * <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
-** You're downloading directly into your root folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
+** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
 * <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
@@ Line 483: / Line 483: @@
 * <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
-** You're downloading directly into your root folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
+** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
 * <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
@@ Line 536: / Line 536: @@
 * <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
-** You're downloading directly into your root folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
+** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder.  This frequently causes issues and is not advised.  To fix this change your download client so it is not placing downloads within your root folder.  Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.
 * <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>

@@ Line 53: / Line 53: @@
 *<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span>
-** 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.
+** 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. Note that Radarr uses <code>libsqlite3.so</code> which may or may not be contained in a sqlite3 upgrade package.
 *<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span>

@@ Line 49: / Line 49: @@
 * <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>
 ** Radarr is written in .Net and requires Mono to run on very old ARM processors.
-** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.
+** Mono 5.20 is the absolute minimum for Radarr.
 ** The upgrade procedure for Mono varies per platform.
@@ Line 133: / Line 133: @@
 * <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>
 ** 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 />
-** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.
+** Mono 5.8 is the absolute minimum for Sonarr, but Mono 5.20 is currently recommended.
 ** The upgrade procedure for Mono varies per platform.
@@ Line 180: / Line 180: @@
 * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span>
-** 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.
+** Newer versions of Lidarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.
 ** Fixing Docker installs
 *** Re-pull your container
@@ Line 203: / Line 203: @@
 *<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>
-** 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.
+** Lidarr is written in .Net and requires Mono to run on very old ARM processors.
-** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
+** Mono 5.20 is the absolute minimum for Lidarr.
 ** See "Update to .NET Core version above"
@@ Line 283: / Line 284: @@
 * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span>
-** 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.
+** Newer versions of Readarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET Core.
 ** Fixing Docker installs
 *** Re-pull your container
@@ Line 306: / Line 307: @@
 *<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>
-** Readarr 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.
+** Readarr is written in .Net and requires Mono to run on very old ARM processors.
-** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
+** Mono 5.20 is the absolute minimum for Readarr.
 ** See "Update to .NET Core version above"

@@ Line 387: / Line 387: @@
 ***** Radarr: <code>/data:/mnt/user/data</code>
 ***** 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."
-*** 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.
+*** 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/hardlinks 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.
 [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

@@ Line 25: / Line 25: @@
 * <span id="update_to_net_core_version">'''[[#update_to_net_core_version|Update to .NET Core version]]'''</span>
-** Newer versions of Radarr are targeted for .NET. We will likely no longer be providing legacy mono builds after 3.1 is released.  You are running one of these legacy builds but your platform supports .NET.
+** Newer versions of Radarr are targeted for .NET. We will no longer be providing legacy mono builds after 3.2 is released.  You are running one of these legacy builds but your platform supports .NET.
 ** Fixing Docker installs
 *** Re-pull your container

@@ Line 112: / Line 112: @@
 *<span id="mono_tls_legacy">'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''</span>
 ** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option
 <section end=radarr_system_status_health_system_warnings />

@@ Line 789: / Line 789: @@
 * Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
 <section end=radarr_system_status_more_info />
 ==== Sonarr ====
 <section begin=sonarr_system_status_more_info />

@@ Line 764: / Line 764: @@
 This will tell you about your current install of Radarr
 <section end=radarr_system_status_about />
 ==== Sonarr ====
 <section begin=sonarr_system_status_about />

@@ Line 400: / Line 400: @@
 ** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.
-* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]'''</span>
+* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
 ** A file accessible via a remote path map appears to have been removed prior to processing completing.
-* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]'''</span>
+* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
 ** Check your logs for more info; Refer to our Troubleshooting Guides
 <section end=radarr_system_status_health_download_clients />
@@ Line 436: / Line 436: @@
 ** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.
-* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]'''</span>
+* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
 ** A file accessible via a remote path map appears to have been removed prior to processing completing.
-* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]'''</span>
+* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
 ** Check your logs for more info; Refer to our Troubleshooting Guides
 <section end="sonarr_system_status_health_download_clients" />
@@ Line 489: / Line 489: @@
 ** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.
-* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]'''</span>
+* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
 ** A file accessible via a remote path map appears to have been removed prior to processing completing.
-* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]'''</span>
+* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
 ** Check your logs for more info; Refer to our Troubleshooting Guides
@@ Line 542: / Line 542: @@
 ** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.
-* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]'''</span>
+* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
 ** A file accessible via a remote path map appears to have been removed prior to processing completing.
-* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]'''</span>
+* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
 ** Check your logs for more info; Refer to our Troubleshooting Guides

@@ Line 229: / Line 229: @@
   RewriteRule /(.*) ws://127.0.0.1:8686/$1 [P,L]
-*<span id="fpcalc_upgrade">'''[[#fpcalc_upgrade|fpcalc needs upgrading]]'''</span>
+*<span id="fpcalc_upgrade">'''[[#fpcalc_upgrade|Fpcalc Needs Upgrading]]'''</span>
-idarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS but must be provided independently on Linux.
+Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS, but must be provided independently on Linux.
 To fix this on a native Linux instance, install the appropriate package using your package manager and make sure that fpcalc is on your PATH (this can be checked using which fpcalc and verifying that the correct location of fpcalc is returned):