+ concreteSetting.getKey() + is malformed ” + proxyBasePath + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” + concreteSetting.getKey() + is malformed ” + proxyBasePath + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

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 “[” + concreteSetting.getKey() + “] is malformed [” + proxyBasePath + “]”classname  is HttpExporter.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// allow the user to configure proxies
 if (Strings.isNullOrEmpty(proxyBasePath) == false) {
 try {
 builder.setPathPrefix(proxyBasePath);
 } catch (final IllegalArgumentException e) {
 throw new SettingsException("[" + concreteSetting.getKey() + "] is malformed [" + proxyBasePath + "]"; e);
 }
 } 
 // allow the user to configure headers that go along with _every_ request
 configureHeaders(builder; config);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content