# Elaticsearch cluster back up is failing - "reason":"RepositoryMissingException"

**URL:** <https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074>\
**Category:** Elasticsearch\
**Tags:** docker, snapshot-and-restore\
**Created:** [February 21, 2023, 2:08pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074 "2023-02-21T14:08:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [February 21, 2023, 2:08pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/1 "2023-02-21T14:08:33Z")

</div>

We've backup repository type as S3, and cluster is running as dockerized AWS EC2, recently snapshot process is failing with reason "reason":"RepositoryMissingException". This error is coming from one of the data node.

Checked POST /\_SNAPSHOT//\_VERIFY  
Returned below error:

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "repository_verification_exception",
        "reason" : "[REPO_NAME] [[NODE_ID, 'RemoteTransportException[[NODE_NAME][NODE_IP:9300][internal:admin/repository/verify]]; nested: RepositoryMissingException[[REPO_NAME] missing];']]"
      }
    ],
    "type" : "repository_verification_exception",
    "reason" : "[REPO_NAME] [[NODE_ID, 'RemoteTransportException[[NODE_NAME][NODE_IP:9300][internal:admin/repository/verify]]; nested: RepositoryMissingException[[REPO_NAME] missing];']]"
  },
  "status" : 500
}

```

Verified inside the docker container, S3 plugin is installed.

Anyone faced this issue?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [February 21, 2023, 2:37pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/2 "2023-02-21T14:37:43Z")

</div>

> [@chateesh](#):
>
> This error is coming from one of the data node.

Is it a new node?

Are you using the client settings (access key and secret key) in `elasticsearch.yml` or on elasticsearch keystore?

If you are using the settings on keystores, check if the keystore for the node has the settings, you need to run [`elasticsearch-keystore list`](https://www.elastic.co/guide/en/elasticsearch/reference/current/elasticsearch-keystore.html#list-settings) on that particular container.

---

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [February 21, 2023, 2:40pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/3 "2023-02-21T14:40:49Z")

</div>

Hi @leandrojmp  
This data node is not a new node, S3 permissions are assigned from EC2 IAM role.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [February 21, 2023, 2:47pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/4 "2023-02-21T14:47:41Z")

</div>

The error you are getting is probably related to permissions issues, but since I never used s3 repositories using EC2 IAM roles, so I can not help further.

Maybe someone else can give more insight.

Do you have anything else in Elasticsearch logs? Check the logs for this container to see if there anything that can give a hint of the issue.

---

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [February 21, 2023, 2:58pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/5 "2023-02-21T14:58:38Z")

</div>

Nothing from logs.  
Thank you for your help.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 21, 2023, 5:42pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/6 "2023-02-21T17:42:15Z")

</div>

What version are you using?

---

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [February 21, 2023, 9:03pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/7 "2023-02-21T21:03:53Z")

</div>

@DavidTurner ES version 5.6.16

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 21, 2023, 9:16pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/8 "2023-02-21T21:16:39Z")

</div>

5.X is very much [EOL](https://www.elastic.co/support/eol) and no longer supported, you should be looking to upgrade as a matter of urgency.

---

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [February 21, 2023, 9:36pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/9 "2023-02-21T21:36:30Z")

</div>

@warkolm Sure.

Do you have any thoughts on the above error.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 21, 2023, 9:37pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/10 "2023-02-21T21:37:21Z")

</div>

You need to upgrade, you are unlikely to get a resolution on such an old, unsupported version sorry to say.

---

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [February 21, 2023, 9:39pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/11 "2023-02-21T21:39:14Z")

</div>

Got it, Thank you @warkolm

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 21, 2023, 9:39pm UTC](https://discuss.elastic.co/t/elaticsearch-cluster-back-up-is-failing-reason-repositorymissingexception/326074/12 "2023-03-21T21:39:34Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
