Cannot access in container : – How to solve related issues

Average Read Time

2 Mins

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 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 ” 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 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

{{mpg_logstarted}}

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



 

Run the Check-Up to get a customized report like this:

Analyze your cluster