Automatically enabling security for older trial license – How to solve related issues

Automatically enabling security for older trial license – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Automatically enabling security for older trial license ” 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: license and plugin.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Automatically enabling security for older trial license ({})” classname is XPackLicenseState.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (isSecurityEnabled == true && isSecurityExplicitlyEnabled == false && mode == OperationMode.TRIAL
                && isSecurityEnabledByTrialVersion == false) {
                // Before 6.3; Trial licenses would default having security enabled.
                // If this license was generated before that version; then treat it as if security is explicitly enabled
                if (mostRecentTrialVersion == null || mostRecentTrialVersion.before(Version.V_6_3_0)) {
                    logger.info("Automatically enabling security for older trial license ({})";
                        mostRecentTrialVersion == null ? "[pre 6.1.0]" : mostRecentTrialVersion.toString());
                    deprecationLogger.deprecated(
                        "Automatically enabling security because the current trial license was generated before 6.3.0. " +
                            "This behaviour will be removed in a future version of Elasticsearch. " +
                            "Please set [{}] to true"; XPackSettings.SECURITY_ENABLED.getKey());




 

Run the Check-Up to get customized recommendations like this:

checklist Run Check-Up

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized code snippet to resolve the issue]

 

 

 

Optimize Elasticsearch Performance

Run The Tool