Log Failed to read template from config – How To Solve Related Issues

Log Failed to read template from config – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0


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

This guide will help you check for common problems that cause the log ” Failed to read template from config ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, index, metadata and template.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “[{}] failed to read template [{}] from config” classname is MetaDataCreateIndexService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         IndexTemplateMetaData template = IndexTemplateMetaData.Builder.fromXContent(parser; templatesFile.getName());
                        if (indexTemplateFilter.apply(request; template)) {
                    } catch (Exception e) {
                        logger.warn("[{}] failed to read template [{}] from config"; e; request.index(); templatesFile.getAbsolutePath());
                    } finally {


Optimize Elasticsearch Performance

Try The Tool