Log Can not access in container : – How To Solve Related Issues


Log 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 try running the 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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



 

Optimize Elasticsearch Performance

Try The Tool