Can not access container – Elasticsearch Log Diagnostic

Get an Elasticsearch Check-Up


Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check

Opster has analyzed this log so you don’t have to
Navigate directly to one of the sections in this page :

Troubleshooting Background – start here to get the full picture       
Log Context – usefull for experts
Related Issues – selected resources from the community  
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check My Elasticsearch 


Troubleshooting background

To troubleshoot Elasticsearch log “Can not access container” it’s important to know common problems related to Elasticsearch concepts: cloud-aws, cloud-azure, container, plugins, repository-azure, storage. See below-detailed explanations complete with common problems, examples and useful tips.


Log Context

Log ”Can not access container” classname is AzureStorageServiceImpl.java
To help get the right context about this log, we have extracted the following from Elasticsearch source code

         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





To help troubleshoot related issues we have gathered selected answers from STOF & Discuss and issues from Github, please review the following for further information :

cannot access elasticsearch in docker for windows linux containers
stackoverflow.com/questions/45395649/cannot-access-elasticsearch-in-docker-for-windows-linux-containers

Number of Views : 0.43 K  Score on Stackoverflow : 1

Kibana on Docker cannot connect to Elasticsearch
stackoverflow.com/questions/40341346/kibana-on-docker-cannot-connect-to-elasticsearch

Number of Views : 16.86 K  Score on Stackoverflow : 29


About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?