# Snapshot status exception **URL:** \ **Category:** Elasticsearch\ **Created:** [September 6, 2017, 11:45am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574 "2017-09-06T11:45:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\ **Post date:** [September 6, 2017, 11:45am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/1 "2017-09-06T11:45:53Z")
Hi I am using ES version 1.5.2 i am opted to take snapshot using following command PUT /\_snapshot/es\_temp/snapshot\_all\_indices\_new { "indices": "index1,index2" , "ignore\_unavailable": "true", "include\_global\_state": false } when i check snapshot status GET /\_snapshot/es\_temp/snapshot\_all\_indices\_new/\_status i am getting the following exception can u please explain me why it is coming Exception message { "error": "IndexShardRestoreFailedException[[index1][0] failed to read shard snapshot file]; nested: FileNotFoundException[/shared/test/es\_bkps/es\_temp/indices/index1/0/snapshot-snapshot\_all\_indices\_new(No such file or directory)]; ", "status": 500 } ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [September 9, 2017, 2:39pm UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/2 "2017-09-09T14:39:10Z")
Is `/shared/test/es_bkps` actually a shared mount between all nodes? ---
**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\ **Post date:** [September 11, 2017, 9:01am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/3 "2017-09-11T09:01:30Z")
hi yes it was shared mount between all nodes.one more point here when i do individual index backup and status check it is working fine. but when i do group of indices backup and status check it is failing ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [September 11, 2017, 10:38am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/4 "2017-09-11T10:38:38Z")
Do you get the same error regardless to what node you issue the command? ---
**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\ **Post date:** [September 11, 2017, 10:57am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/5 "2017-09-11T10:57:48Z")
yes i have two nodes in my cluster and i have tested on both nodes still getting same error ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [September 11, 2017, 11:00am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/6 "2017-09-11T11:00:47Z")
Can you post here the output of `ls -al /shared/test/es_bkps/es_temp/indices/` from inside both nodes? ---
**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\ **Post date:** [September 11, 2017, 11:07am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/7 "2017-09-11T11:07:26Z")
hi here is the output of the command please node 1: drwxr-xr-x. 11 nobody nobody 4096 Sep 11 05:56 . drwxr-xr-x. 3 nobody nobody 122 Sep 11 05:56 .. drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index1 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index2 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index3 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index4 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index5 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index6 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index7 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index8 node 2: drwxr-xr-x. 11 nobody nobody 4096 Sep 11 05:56 . drwxr-xr-x. 3 nobody nobody 122 Sep 11 05:56 .. drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index1 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index2 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index3 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index4 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index5 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index6 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index7 drwxr-xr-x. 2 nobody nobody 51 Sep 11 05:56 index8 ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [September 11, 2017, 11:54am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/8 "2017-09-11T11:54:35Z")
I could not reproduce your issue and your setup seems to be fine. Also, even though 1.5 is rather old and many bugs has been fixed, I could not find any relevant issue related to this error. I suggest that you check NFS logs both the clients and also in the server and look for potential problems. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 9, 2017, 11:54am UTC](https://discuss.elastic.co/t/snapshot-status-exception/99574/9 "2017-10-09T11:54:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.