Can not access container – How to solve related issues

Average Read Time

2 Mins

Can not access container – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Can not access container ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, cloud-azure, container, plugins and repository-azure.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “can not access container [{}]” classname is AzureStorageServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         try {
            CloudBlobClient client = this.getSelectedClient(account; mode);
            CloudBlobContainer blob_container = client.getContainerReference(container);
            return blob_container.exists();
        } catch (Exception e) {
            logger.error("can not access container [{}]"; container);
        }
        return false;
    }

    
Override



 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content