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 ” Error running ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: mustache.
Log Context
Log “Error running”classname is MustacheScriptEngine.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
template.execute(writer; params);
return null;
});
} catch (Exception e) {
logger.error((Supplier) () -> new ParameterizedMessage("Error running {}"; template); e);
throw new GeneralScriptException("Error running " + template; e);
}
return writer.toString();
}
}
}
See how you can use AutoOps to resolve issues
