Expected hexadecimal at offset; found – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration 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.

This guide will help you check for common problems that cause the log ” expected hexadecimal at offset; found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Log Context

Log “{}expected hexadecimal at offset[{}]; found [{}]”classname  is ExpressionBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (pos > i) {
 if (inspect && HEXA.indexOf(lowerCase.charAt(i)) < 0) {
 throw new ParsingException(source; "{}expected hexadecimal at offset[{}]; found [{}]"; errorPrefix; i; string.charAt(i));
 return new Literal(source(ctx); string; DataTypes.KEYWORD);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content