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 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 ” Can not initialize container : ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-azure, 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 to analyze Elasticsearch configuration and help resolve this error.

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();
    }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content