Store location – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.13

Briefly, this error occurs when Elasticsearch cannot access the data directory due to permission issues or the directory being non-existent. To resolve this, ensure that the directory specified in the setting in the Elasticsearch configuration file exists and has the correct permissions. Alternatively, you can change the setting to a directory that does exist and has the correct permissions. Also, ensure that the Elasticsearch process has the necessary permissions to read and write to this directory.

This guide will help you check for common problems that cause the log ” store location [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, blobstore.

Log Context

Log “store location [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else {
 BlobContainer testBlobContainer = blobStore().blobContainer(basePath().add(testBlobPrefix(seed)));
 try {
 testBlobContainer.writeBlob("data-" + localNode.getId() + ".dat"; new BytesArray(seed); true);
 } catch (Exception exp) {
 throw new RepositoryVerificationException(; "store location [" + blobStore() +
 "] is not accessible on the node [" + localNode + "]"; exp);
 try (InputStream masterDat = testBlobContainer.readBlob("master.dat")) {
 final String seedRead = Streams.readFully(masterDat).utf8ToString();
 if (seedRead.equals(seed) == false) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?