# Snapshots are failing

**URL:** <https://discuss.elastic.co/t/snapshots-are-failing/262769>\
**Category:** Elasticsearch\
**Created:** [January 31, 2021, 10:29pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769 "2021-01-31T22:29:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SteveHodges](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)\
**Post date:** [January 31, 2021, 10:29pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769/1 "2021-01-31T22:29:59Z")

</div>

After a network outage, the elasticsearch snapshot is failing. After I restored the connection to the NAS I am getting errors when I try to take a snapshot.

The error is access\_denied\_exception

Here is the command I run to verify the snapshots and the error I get

`curl -X POST "192.168.1.8:9200/_snapshot/DM_backup/_verify"`

```auto
{"error":{"root_cause":[{"type":"exception","reason":"failed to create blob container"}],"type":"exception","reason":"failed to create blob container","caused_by":{"type":"access_denied_exception","reason":"/mnt/nasbackup/dm-logserver/NAS_backup_location/tests-Ly03ASkJR8WkWUrA4UAflg"}},"status":500}

```

I also tried to delete the oldest snapshot.

`sudo curl -X DELETE "10.134.90.8:9200/_snapshot/DM_backup/snapshot_5?pretty"`  
Output from trying to delete the a snapshot

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "access_denied_exception",
        "reason" : "/mnt/nasbackup/dm-logserver/NAS_backup_location/pending-index-47-TiO4j11eTYChkZ0iw8MLHw"
      }
    ],
    "type" : "access_denied_exception",
    "reason" : "/mnt/nasbackup/dm-logserver/NAS_backup_location/pending-index-47-TiO4j11eTYChkZ0iw8MLHw"
  },
  "status" : 500
}

```

The snapshot is a NAS which is mounted

` mount.cifs -v //192.168.2.203/public /mnt/nasbackup -o vers=1.0,rw,username=user1,password= ******* `

I have tried to change ownership to 777 as test. although the command is successful, the permissions don't change.

```auto
total 1031
drwxr-xr-x 2 root root 0 Jan 31 2021 .
drwxr-xr-x 2 root root 0 Jan 31 2021 ..
-rwxr-xr-x 1 root root 137326 Dec 17 15:26 index-32
-rwxr-xr-x 1 root root 8 Dec 17 15:26 index.latest
drwxr-xr-x 2 root root 0 Dec 17 15:08 indices
-rwxr-xr-x 1 root root 171992 Dec 17 15:26 meta-6n4XFTmnRkiuto2guP6lKA.dat
-rwxr-xr-x 1 root root 171992 Dec 3 08:49 meta-KnEHI40CReeWfmFPxla1QQ.dat
-rwxr-xr-x 1 root root 171992 Nov 30 12:39 meta-U0KwAyv2QkGFXIQtxKsARQ.dat
-rwxr-xr-x 1 root root 171992 Dec 10 13:02 meta-vjh2h4I-RBW5WN93n1zBcw.dat
-rwxr-xr-x 1 root root 171992 Nov 13 10:33 meta-wvy7ALr-Qq6Kiqo5-4A5OA.dat
-rwxr-xr-x 1 root root 10887 Dec 17 15:26 snap-6n4XFTmnRkiuto2guP6lKA.dat
-rwxr-xr-x 1 root root 11056 Dec 3 08:49 snap-KnEHI40CReeWfmFPxla1QQ.dat
-rwxr-xr-x 1 root root 11659 Nov 30 12:39 snap-U0KwAyv2QkGFXIQtxKsARQ.dat
-rwxr-xr-x 1 root root 11639 Dec 10 13:02 snap-vjh2h4I-RBW5WN93n1zBcw.dat
-rwxr-xr-x 1 root root 11032 Nov 13 10:33 snap-wvy7ALr-Qq6Kiqo5-4A5OA.dat

```

Any advice would be appreciated.

---

<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:** [January 31, 2021, 10:38pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769/2 "2021-01-31T22:38:35Z")

</div>

Have you tried remounting the FS?

---

<div class="post-metadata">

**Author:** ![SteveHodges](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)\
**Post date:** [February 1, 2021, 2:56pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769/3 "2021-02-01T14:56:44Z")

</div>

Yes, I have tried that already. FYI, I can create a text file as root.

---

<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 1, 2021, 4:11pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769/4 "2021-02-01T16:11:19Z")

</div>

The files in the repository appear to be owned by `root` and apparently cannot be modified by other users. You need to adjust _something_ so that they become writable by the user as which Elasticsearch is running (which is not `root`). Unfortunately I've no idea what that "something" is, it will depend on how your NAS is configured and how it's mounted.

---

<div class="post-metadata">

**Author:** ![SteveHodges](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)\
**Post date:** [February 1, 2021, 7:52pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769/5 "2021-02-01T19:52:46Z")

</div>

Thank you. This is what I thought, but I wanted to make sure.

How I am mounting is show in the post if that helps.

---

<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 1, 2021, 7:52pm UTC](https://discuss.elastic.co/t/snapshots-are-failing/262769/6 "2021-03-01T19:52:53Z")

</div>

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