Difference between revisions of "System status"

From Servarr
Line 40: Line 40:
 
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
 
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
 
** See "Update to .NET Core version above"
 
** See "Update to .NET Core version above"
 +
 +
*<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.
  
 
*<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span>
 
*<span id="new_update_is_available">'''[[#new_update_is_available|New update is available]]'''</span>

Revision as of 17:53, 25 January 2021

System

Health

Overview

Radarr

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.

Sonarr

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.

Lidarr

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.

Readarr

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.

System Warnings

Radarr
  • Update to .NET Core version
    • 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.
    • Fixing Docker installs
      • Re-pull your container
    • Fixing Standalone installs
      • This should only happen on Linux hosts. Do not install .net core runtime or SDK from microsoft. To remedy, download the correct build for your architecture:
      • Back-Up your existing configuration before the next step.
      • Delete your existing binaries' (contents or folder of /opt/Radarr) and replace with the contents of the .tar.gz you just downloaded.
      • DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.
        YOU MUST DELETE THE OLD ONES FIRST        .
        • Update your startup script to call Radarr instead of calling it with mono like mono --debug Radarr.exe. In other words you want, as an example, /opt/Radarr/Radarr and not mono --debug /opt/Radarr/Radarr.
      • If Radarr doesn’t start, ensure you have the dependencies listed here installed.
  • Mono version is less than 5.8, upgrade for improved stability
    • 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.
    • Mono version 5.x and higher are also available and provides a better experience on certain platforms.
    • See "Update to .NET Core version above"
  • New update is available
    • 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 -> Updates page is probably a good starting point.
    • (This warning will not appear if your current version is less than 14 days old)
  • Updating will not be possible to prevent deleting AppData on Update
    • Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be C:\ProgramData for Windows and, ~/.config for linux.
    • Please look at System -> Info to see the current AppData & Startup directories.
    • This means Radarr will be unable to update itself without risking data-loss.
    • 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 ~/.config/Radarr directory to preserve your database.
  • Branch is for a previous version
    • 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.
  • Could not connect to signalR
    • 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.
    • 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:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

Include /etc/apache2/mods-available/proxy_wstunnel.load
ProxyPass "/socket" "ws://127.0.0.1:7878/socket"
ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"
  • For Caddy (V1) use this:
    • Note: you'll also need to add the websocket directive to your radarr configuration
 proxy /radarr 127.0.0.1:7878 {
     websocket
     transparent
 }


Sonarr
  • Currently installed .Net Framework is old and unsupported
    • 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.
    • 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.
  • Currently installed mono version is old and unsupported
    • 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.
    • Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.
    • The upgrade procedure for Mono varies per platform.
  • Currently installed mono version is supported but upgrading is recommended
    • 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.
    • The upgrade procedure for Mono varies per platform.
  • New update is available
    • 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 -> 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.
    • (This warning will not appear if your current version is less than 14 days old)
  • Updating will not be possible to prevent deleting AppData on Update
    • Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be C:\ProgramData for Windows and, ~/.config for linux.
    • Please look at System -> About to see the current AppData & Startup directories.
    • This means Sonarr will be unable to update itself without risking data-loss.
    • 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 ~/.config/Sonarr directory to preserve your database.
  • Could not connect to signalR
    • 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.
    • 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:
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    Include /etc/apache2/mods-available/proxy_wstunnel.load
    ProxyPass "/socket" "ws://127.0.0.1:7878/socket"
    ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"


Lidarr
  • Update to .NET Core version
    • 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.
    • Fixing Docker installs
      • Re-pull your container
    • Fixing Standalone installs
      • This should only happen on Linux hosts. Do not install .net core runtime or SDK from microsoft. To remedy, download the correct build for your architecture:
      • Back-Up your existing configuration before the next step.
      • Delete your existing binaries' (contents or folder of /opt/Lidarr) and replace with the contents of the .tar.gz you just downloaded.
      • DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.
        YOU MUST DELETE THE OLD ONES FIRST        .
        • Update your startup script to call Lidarr instead of calling it with mono like mono --debug Lidarr.exe. In other words you want, as an example, /opt/Lidarr/Lidarr and not mono --debug /opt/Lidarr/Lidarr.
      • If Lidarr doesn’t start, ensure you have the dependencies listed here installed
  • Mono version is less than 5.8, upgrade for improved stability
    • 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.
    • Mono version 5.x and higher are also available and provides a better experience on certain platforms.
    • See "Update to .NET Core version above"
  • New update is available
    • 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 -> Updates page is probably a good starting point.
    • (This warning will not appear if your current version is less than 14 days old)
  • Branch is for a previous version
    • 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.
    • 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.
  • Could not connect to signalR
    • 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.
    • 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:
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    Include /etc/apache2/mods-available/proxy_wstunnel.load
    ProxyPass "/socket" "ws://127.0.0.1:7878/socket"
    ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"
Readarr
  • Update to .NET Core version
    • 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.
    • Fixing Docker installs
      • Re-pull your container
    • Fixing Standalone installs
      • This should only happen on Linux hosts. Do not install .net core runtime or SDK from microsoft. To remedy, download the correct build for your architecture:
      • Back-Up your existing configuration before the next step.
      • Delete your existing binaries' (contents or folder of /opt/Readarr) and replace with the contents of the .tar.gz you just downloaded.
      • DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.
        YOU MUST DELETE THE OLD ONES FIRST        .
        • Update your startup script to call Readarr instead of calling it with mono like mono --debug Readarr.exe. In other words you want, as an example, /opt/Readarr/Readarr and not mono --debug /opt/Readarr/Readarr.
      • If Readarr doesn’t start, ensure you have the dependencies listed here installed.
  • Mono version is less than 5.2, upgrade for improved stability
    • 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.
    • Mono version 5.x and higher are also available and provides a better experience on certain platforms.
    • See "Update to .NET Core version above"
  • New update is available
    • 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 -> Updates page is probably a good starting point.
    • (This warning will not appear if your current version is less than 14 days old)
  • Branch is for a previous version
    • 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.
    • 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.
  • Could not connect to signalR
    • 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.
    • 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:
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    Include /etc/apache2/mods-available/proxy_wstunnel.load
    ProxyPass "/socket" "ws://127.0.0.1:7878/socket"
    ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"


Download Clients

Radarr
  • No download client is available
    • 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 -> Download Client.
  • Unable to communicate with download client
    • 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.
    • This is typically due to improperlly configured download client. Things you can typically check:
      • Your download clients IP Address if its on the same bare metal machien this is typically 127.0.0.1
      • 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.
      • Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See here for more information on this one in our FAQ.
  • Download clients are unavailable due to failure
    • 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.
    • You should inspect System->Logs to see what the reason is for the failures.
    • If you no longer use this download client, disable it in Radarr to prevent the errors.
  • Enable Completed Download Handling
    • 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.
    • (Completed Download Handling is enabled by default for new users.)
  • Docker bad remote path mapping
    • This error is typically associated with bad docker paths within either your download client or Radarr
      • An example of this would be:
        • Download client: Download Path: /downloads:/mnt/user/downloads
        • Radarr: Download Path: /data:/mnt/user/downloads
        • Within this example the download client places its downloads into /downloads and therefore tells Radarr when its complete that the finished movie is in /downloads. Radarr then comes along and says "Okay, cool, let me check in /downloads" Well, inside Radarr you did not allocate a /downloads path you allocated a /data path so it throws this error.
        • The easiest fix for this is CONSISTENCY if you use one scheme in your download client, use it across the board.
        • Team Radarr is a big fan of simply using /data.
          • Download client: /data:/mnt/user/data
          • Radarr: /data:/mnt/user/data
          • Now within the download client you can specify where in /data 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." /data/torrents (or usenet)/movies and since you used /data in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a /data and I also can see /torrents (or usenet)/movies 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 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.


Sonarr
  • No download client is available
    • 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 -> Download Client.
  • Unable to communicate with download client
    • 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.
  • Download clients are unavailable due to failure
    • 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.
    • You should inspect System->Logs to see what the reason is for the failures.
    • If you no longer use this download client, disable it in Sonarr to prevent the errors.


Lidarr
  • No download client is available
    • 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 -> Download Client.
  • Unable to communicate with download client
    • 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.
    • This is typically due to improperlly configured download client. Things you can typically check:
      • Your download clients IP Address if its on the same bare metal machien this is typically 127.0.0.1
      • 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.
      • Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See here for more information on this one in our FAQ.
  • Download clients are unavailable due to failure
    • 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.
    • You should inspect System->Logs to see what the reason is for the failures.
    • If you no longer use this download client, disable it in Lidarr to prevent the errors.
  • Enable Completed Download Handling
    • 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.
    • (Completed Download Handling is enabled by default for new users.)
  • Docker bad remote path mapping
    • This error is typically associated with bad docker paths within either your download client or Lidarr
      • An example of this would be:
        • Download client: Download Path: /downloads:/mnt/user/downloads
        • Lidarr: Download Path: /data:/mnt/user/downloads
        • Within this example the download client places its downloads into /downloads and therefore tells Lidarr when its complete that the finished movie is in /downloads. Lidarr then comes along and says "Okay, cool, let me check in /downloads" Well, inside Lidarr you did not allocate a /downloads path you allocated a /data path so it throws this error.
        • The easiest fix for this is CONSISTENCY if you use one scheme in your download client, use it across the board.
        • Team Lidarr is a big fan of simply using /data.
          • Download client: /data:/mnt/user/data
          • Lidarr: /data:/mnt/user/data
          • Now within the download client you can specify where in /data 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." /data/torrents (or usenet)/movies and since you used /data in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a /data and I also can see /torrents (or usenet)/movies 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 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.
Readarr
  • No download client is available
    • 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 -> Download Client.
  • Unable to communicate with download client
    • 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.
    • This is typically due to improperlly configured download client. Things you can typically check:
      • Your download clients IP Address if its on the same bare metal machien this is typically 127.0.0.1
      • 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.
      • Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See here for more information on this one in our FAQ.
  • Download clients are unavailable due to failure
    • 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.
    • You should inspect System->Logs to see what the reason is for the failures.
    • If you no longer use this download client, disable it in Readarr to prevent the errors.
  • Enable Completed Download Handling
    • 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.
    • (Completed Download Handling is enabled by default for new users.)
  • Docker bad remote path mapping
    • This error is typically associated with bad docker paths within either your download client or Readarr
      • An example of this would be:
        • Download client: Download Path: /downloads:/mnt/user/downloads
        • Readarr: Download Path: /data:/mnt/user/downloads
        • Within this example the download client places its downloads into /downloads and therefore tells Radarr when its complete that the finished movie is in /downloads. Readarr then comes along and says "Okay, cool, let me check in /downloads" Well, inside Readarr you did not allocate a /downloads path you allocated a /data path so it throws this error.
        • The easiest fix for this is CONSISTENCY if you use one scheme in your download client, use it across the board.
        • Team Readarr is a big fan of simply using /data.
          • Download client: /data:/mnt/user/data
          • Readarr: /data:/mnt/user/data
          • Now within the download client you can specify where in /data 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." /data/torrents (or usenet)/movies and since you used /data in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a /data and I also can see /torrents (or usenet)/movies 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 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.


Completed/Failed Download Handling

Radarr
  • Completed Download Handling is disabled
    • (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.)
    • 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.
    • 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)
    • You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.
    • 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.
    • 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 -> 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.


Sonarr
  • Completed Download Handling is disabled
    • (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.)
    • 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.
    • 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 Sonarr 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 Sonarr 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)

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.

    • 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 -> 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.


Lidarr
  • Completed Download Handling is disabled
    • (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.)
    • 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.
    • 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)
    • You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.
    • 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.
    • 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 -> 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.


Readarr
  • Completed Download Handling is disabled
    • (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.)
    • 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.
    • 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)
    • You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.
    • 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.
    • 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 -> 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.


Indexers

Radarr
  • No indexers are enabled
  • Enabled indexers do not support searching
    • 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.
  • Indexers are unavailable due to failures
    • 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).
    • 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.
    • You can prevent the warning by disabling the affected indexer.
    • 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.


Sonarr
  • No indexers are enabled
  • Enabled indexers do not support searching
    • 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.
  • Indexers are unavailable due to failures
    • 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).
    • 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.
    • You can prevent the warning by disabling the affected indexer.
    • 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.
Lidarr
  • Enabled indexers do not support searching
    • 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.
  • Indexers are unavailable due to failures
    • 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).
    • 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.
    • You can prevent the warning by disabling the affected indexer.
    • 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.
Readarr
  • Enabled indexers do not support searching
    • 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.
  • Indexers are unavailable due to failures
    • 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).
    • 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.
    • You can prevent the warning by disabling the affected indexer.
    • 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.


Folders

Radarr
  • Missing root folder
    • This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
      • 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
        1. Easiest way to find this is to go to the Movies (Library) Tab
        2. Create a custom filter with the old root folder path
        3. 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.
        4. 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
Sonarr
  • Missing root folder
    • This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
      • 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
        1. Go to the Series > Mass Editor Tab
        2. Create a custom filter with the old root folder path
        3. 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.
        4. 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
Lidarr
  • Missing root folder
    • This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
      • 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
        1. Go to the Library > Mass Editor Tab
        2. Create a custom filter with the old root folder path
        3. 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.
        4. 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
Readarr
  • Missing root folder
    • This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
      • 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
        1. Go to the Library > Mass Editor Tab
        2. Create a custom filter with the old root folder path
        3. 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.
        4. 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


Media

Radarr
  • Movie was removed from TMDb
    • 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.
    • 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
  • Lists are unavailable due to failures
    • 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.
Sonarr
  • Series Removed from TheTVDB
    • 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.
Lidarr

Text

Readarr

Text


Disk Space

Radarr

  • This section will show you available disk space
    • In docker this can be tricky as it will typically show you the available space w/in your Docker image

Sonarr

  • This section will show you available disk space
    • In docker this can be tricky as it will typically show you the available space w/in your Docker image

Lidarr

  • This section will show you available disk space
    • In docker this can be tricky as it will typically show you the available space w/in your Docker image

Readarr

  • This section will show you available disk space
    • In docker this can be tricky as it will typically show you the available space w/in your Docker image


About

Radarr

This will tell you about your current install of Radarr


Sonarr

This will tell you about your current install of Radarr

Lidarr

This will tell you about your current install of Lidarr

Readarr

This will tell you about your current install of Readarr


More Info

Radarr


Sonarr

  • Home page: Radarr's home page
  • Forums: [forums.sonarr.tv Official Sonarr Forums]
  • Discord: [discord.gg/M6BvZn5 Join our discord]
  • Reddit: [1]
  • Twitter: [@sonarrtv]
  • IRC: #sonarr on Freenode
  • Wiki: You're here already
  • Donations: If you're feeling generous and would like to donate click here
  • Source: [github.com/Sonarr/Sonarr Github]
  • Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]

Lidarr

Readarr


Templates

Retrieved from "https://wikiold.servarr.com/index.php?title=System_status&oldid=3067"