Log Cannot access in container : – How To Solve Related Issues



Log Cannot 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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Cannot 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, 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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

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

     public void delete(BlobPath path) throws IOException {
        final String keyPath = path.buildAsString();
        try {
            service.deleteFiles(clientName; container; keyPath);
        } catch (URISyntaxException | StorageException e) {
            logger.warn("cannot access [{}] in container {{}}: {}"; keyPath; container; e.getMessage());
            throw new IOException(e);
        }
    }

    
Override








Find Configuration Errors

Try The Tool