How To Solve Issues Related to Log – Can not start azure client:

How To Solve Issues Related to Log – Can not start azure client:

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Can not start azure client:” it’s important to understand a few problems related to Elasticsearch concepts cloud-aws, cloud-azure, plugins, repository-azure. See bellow important tips and explanations on these concepts

Log Context

Log”can not start azure client: {}” classname is AzureComputeServiceImpl.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         Configuration configuration;
        try {
            configuration = ManagementConfiguration.configure(new URI(Azure.ENDPOINT);
                    subscriptionId; keystorePath; keystorePassword; keystoreType);
        } catch (IOException|URISyntaxException e) {
            logger.error("can not start azure client: {}"; e.getMessage());
            computeManagementClient = null;
            return;
        }
        logger.trace("creating new Azure client for [{}]; [{}]"; subscriptionId; serviceName);
        computeManagementClient = ComputeManagementService.create(configuration);




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

 

Error While Creating Elasticsearch  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now