Unable to check if bucket ” + bucketName + ” exists – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Unable to check if bucket ” + bucketName + ” exists ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, plugins and repository-gcs.

Log Context

Log “Unable to check if bucket [” + bucketName + “] exists”classname  is GoogleCloudStorageBlobStore.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

private boolean doesBucketExist(String bucketName) {
 try {
 final Bucket bucket = SocketAccess.doPrivilegedIOException(() -> client().get(bucketName));
 return bucket != null;
 } catch (final Exception e) {
 throw new BlobStoreException("Unable to check if bucket [" + bucketName + "] exists"; e);
 * List blobs in the specific bucket under the specified path. The path root is removed.


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content