System status

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. To remedy, download the correct build for your architecture:
      • x64
      • arm64
      • arm
    • Back-Up your existing configuration before the next step.
    • Delete your existing binaries 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 mono --debug Radarr.exe
    • If Radarr doesn’t start make sure you have the dependencies listed here installed.
• Mono version is less than 3.10, 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 4.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)
• Cannot install update because startup folder is not writable by the user
  • 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.
• 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.
  • 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.
• 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;

  • Make sure you do not include proxy_set_header Connection "Upgrade"; as suggested by the nginx documentation. THIS WILL NOT WORK
  • See https://github.com/aspnet/AspNetCore/issues/17081
  • For apache reverse proxy you need to add to the configuration:

  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"

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.

• 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 .Net Framework is supported but upgrading is recommended
  • 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.
  • 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)
• Cannot install update because startup folder is not writable by the user
  • 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.
• 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.

Lidarr

Text

Readarr

Text

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

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.
• Enable Completed Download Handling or configure Drone Factory
  • 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.
  • (Completed Download Handling is enabled by default for new users.)

Lidarr

Text

Readarr

Text

Drone Factory

Radarr

• Drone Factory
  • Drone Factory folder does not exist
    • If you configure Radarr to use a Drone Factory the specified folder must exist. Please ensure that it indeed exists, or disable the Drone Factory.
    • (You might want to consider using Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients.)
  • Unable to write to Drone Factory folder
    • You configured Radarr to use a Drone Factory, however Radarr was unable to creates a test file, this indicates permission issues. Please verify that the user Radarr runs under has the appropriate permissions.
  • Drone Factory is deprecated
    • Please don’t panic.
    • The Drone Factory is unreliable in various situations and has been replaced by Completed Download Handling and external API calls over a year ago. This functionality will be removed in a future major version of Radarr and should no longer be used. Please note that the Drone Factory periodic scan functionality will not be removed via an automatic update, but rolled into an future backward-incompatible v3 major release which in most cases will require manual installation.
    • For occasional manual downloads use Wanted->Manual Import. It’ll allow you to select a directory and optionally review the parsing results before actually importing. Useful for the occasional manual download that isn’t handled automatically.
    • If the download client is on a remote machine, consider using remote mounts in combination with Settings->Download Clients->Remote Path Mapping to make Radarr aware of the mount. Alternatives are available.
    • Please disable the Drone Factory:
      • Go to Settings->Download Clients
      • Enable Advanced Settings in the top left
      • Make sure the Drone Factory field is empty
      • Make sure the Drone Factory Interval field is set to 0
      • Save settings

Sonarr

Text

Lidarr

Text

Readarr

Text

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 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.
  • 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.
• Download Client has history items in Drone Factory conflicting with Completed Download Handling
  • The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Radarr will ignore those downloads during it’s Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.
  • Resolution: Configure the Drone Factory to use a different folder.

TODO: Reword

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 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.
  • 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)
      
  • You should reconfigure Sonarr 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. 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.
• Download Client has history items in Drone Factory conflicting with Completed Download Handling
  • The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Sonarr will ignore those downloads during it's Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.
  • Resolution: Configure the Drone Factory to use a different folder.
  • TODO: Reword

Lidarr

Text

Readarr

Text

Indexers

Radarr

• No indexers are enabled
  • Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.
• 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
  • Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.
• 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

Text

Readarr

Text

Folders

Radarr

• Missing root folder
  • This message may appear if a previous root folder is no longer used. To remove old root folders:
    • Begin adding a new Movie* by searching for a name, but do not submit
    • In the 'Path' dropdown, select 'Add a different path'
    • Click the cross at the end of a row to remove the unused path
  • 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.
  • 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.
    • NB: I thought Radarr was for Movies and not Series

Sonarr

• Missing root folder
  • This message may appear if a previous root folder is no longer used. To remove old root folders:
    1. Begin adding a new Series by searching for a name, but do not submit
    2. In the 'Path' dropdown, select 'Add a different path'
    3. Click the cross at the end of a row to remove the unused path
  • 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.
  • 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.

Lidarr

Text

Readarr

Text

Media

Radarr

• Movie was removed from TMDb
  • 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.
    
  • 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

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

Text

Lidarr

Text

Readarr

Text

About

Radarr

This will tell you about your current install of Radarr

Sonarr

Text

Lidarr

Text

Readarr

Text

More Info

Radarr

• Home page: Radarr's home page
• Discord: Join our discord
• Wiki: You're here already
• Donations: If you're feeling generous and would like to donate click here
• Source: Github
• Feature Requests: Got as great idea drop it here

Sonarr

Text

Lidarr

Text

Readarr

Text