Expected hexadecimal at offset found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch encounters non-hexadecimal characters in a place where it expects hexadecimal characters. This could be due to incorrect data input or a malformed request. To resolve this issue, you should first check the data or request causing the error. Ensure that it only contains valid hexadecimal characters (0-9, A-F). If the error persists, it might be due to a bug in your Elasticsearch version. Consider updating to the latest stable version.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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, plugin.

Log Context

Log “{}expected hexadecimal at offset[{}]; found [{}]” class name 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);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?