Opster Team
Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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. Take a self-guided product tour to see for yourself (no registration required).
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 :
AccessController.doPrivileged((PrivilegedAction) () -> { 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(); } }
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 2 minutes
Jose Rafaelly
Head of System Engineering at Everymundo