Can not start azure client: – 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 start azure client: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, cloud-azure, plugins 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 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);




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content