Type to search.

Diagnose invalid repositories

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

When an Elasticsearch node faces an unexpected exception when trying to instantiate a snapshot repository, it will mark the repository as "invalid" and write a warning to the log file. Use the following steps to diagnose the underlying cause of this issue:

  1. Retrieve the affected nodes from the affected resources section of the health report.
  2. Refer to the logs of the affected node(s) and search for the repository name. You should be able to find logs that will contain relevant exception.
  3. Try to resolve the errors reported.