# Elasticsearch GCS snapshots RepositoryException

**URL:** <https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [June 6, 2023, 12:08pm UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336 "2023-06-06T12:08:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![navaneethan](https://avatars.discourse-cdn.com/v4/letter/n/f17d59/32.png) [@navaneethan](https://discuss.elastic.co/u/navaneethan)\
**Post date:** [June 6, 2023, 12:08pm UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336/1 "2023-06-06T12:08:08Z")

</div>

Hi Team,

We are suddenly facing the snapshot exception in GCS  
with

[2023-06-05T11:40:34,219][WARN][r.suppressed] [###] path: /\_snapshot/e#-repo/###\_gcs\_ss\_2023-06-05-1130, params: {pretty=true, repository=###-###-repo, snapshot=###\_gcs\_ss\_2023-06-05-1130}  
org.elasticsearch.repositories.RepositoryException: [###-###-repo] could not read repository data from index blob

Caused by: com.fasterxml.jackson.core.io.JsonEOFException: Unexpected end-of-input in VALUE\_STRING  
at [Source: sun.nio.ch.ChannelInputStream@171ce462; line: 1, column: 14681217]

and we are not able to access the repo

{  
"error": {  
"root\_cause": [  
{  
"type": "repository\_exception",  
"reason": "[###-repo] could not read repository data from index blob"  
}  
],  
"type": "repository\_exception",  
"reason": "[###-repo] could not read repository data from index blob",  
"caused\_by": {  
"type": "json\_e\_o\_f\_exception",  
"reason": "Unexpected end-of-input in VALUE\_STRING\n at [Source: sun.nio.ch.ChannelInputStream@768613c2; line: 1, column: 14681217]"  
}  
},  
"status": 500  
}

---

<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:** [June 8, 2023, 11:00pm UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336/2 "2023-06-08T23:00:46Z")

</div>

@DavidTurner sorry to ping you directly here but this seems right in your area of expertise.

---

<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:** [June 9, 2023, 4:36am UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336/3 "2023-06-09T04:36:13Z")

</div>

No problem Mark

What version are you running @navaneethan ?

---

<div class="post-metadata">

**Author:** ![navaneethan](https://avatars.discourse-cdn.com/v4/letter/n/f17d59/32.png) [@navaneethan](https://discuss.elastic.co/u/navaneethan)\
**Post date:** [June 9, 2023, 2:29pm UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336/4 "2023-06-09T14:29:34Z")

</div>

We are using es 7.3 version but this is not related to the gcs bucket we are using for the snapshots

---

<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:** [June 9, 2023, 2:46pm UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336/5 "2023-06-09T14:46:32Z")

</div>

Ok that version is _very_ old, long past EOL. I remember we fixed an issue that would explain this a few years ago. You need to upgrade as a matter of urgency.

---

<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:** [July 7, 2023, 2:46pm UTC](https://discuss.elastic.co/t/elasticsearch-gcs-snapshots-repositoryexception/335336/6 "2023-07-07T14:46:40Z")

</div>

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