Updating existing license to the new version.nnOld license:n nn New license:n – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Updating existing license to the new version.nnOld license:n nn New license:n ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: license, plugin, task and version.

Log Context

Log “Updating existing license to the new version.nnOld license:n {}nn New license:n{}” classname is StartupSelfGeneratedLicenseTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        License selfGeneratedLicense = SelfGeneratedLicense.create(specBuilder; currentState.nodes());
        Version trialVersion = currentLicenseMetaData.getMostRecentTrialVersion();
        LicensesMetaData newLicenseMetadata = new LicensesMetaData(selfGeneratedLicense; trialVersion);
        mdBuilder.putCustom(LicensesMetaData.TYPE; newLicenseMetadata);
        logger.info("Updating existing license to the new version.\n\nOld license:\n {}\n\n New license:\n{}";
            license; newLicenseMetadata.getLicense());
        return ClusterState.builder(currentState).metaData(mdBuilder).build();



Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content