Log Can not initialize container : – How To Solve Related Issues



Log Can not initialize container : – How To Solve Related Issues

Opster Team

Feb-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 “Can not initialize 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: cloud-azure, 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 “can not initialize container [{}]: [{}]” classname is AzureRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 if (!blobStore.doesContainerExist(blobStore.container())) {
                    logger.debug("container [{}] does not exist. Creating..."; blobStore.container());
                    blobStore.createContainer(blobStore.container());
                }
            } catch (StorageException | URISyntaxException e) {
                logger.warn("can not initialize container [{}]: [{}]"; blobStore.container(); e.getMessage());
                throw new RepositoryVerificationException(repositoryName; "can not initialize container " + blobStore.container(); e);
            }
        }
        return super.startVerification();
    }









Find Configuration Errors

Try The Tool