Can not access in container : – How to solve related issues

Average Read Time

2 Mins

Can not access in container : – How to solve related issues

Opster Team

Jan-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 in container : ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: container, plugins, repositories 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 [{}] in container {{}}: {}” classname is AzureBlobContainer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     public boolean blobExists(String blobName) {
        logger.trace("blobExists({})"; blobName);
        try {
            return blobStore.blobExists(buildKey(blobName));
        } catch (URISyntaxException | StorageException | IOException e) {
            logger.warn("can not access [{}] in container {{}}: {}"; blobName; blobStore; e.getMessage());
        }
        return false;
    }

    
Override



 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content