Log Skipping unknown custom object with type – How To Solve Related Issues

Log Skipping unknown custom object with type – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “Skipping unknown custom object with type” it’s important to understand a few problems related to Elasticsearch concepts cluster, metadata. See bellow important tips and explanations on these concepts

Log Context

Log”Skipping unknown custom object with type {}” classname is MetaData.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     } else {
                        try {
                            Custom custom = parser.namedObject(Custom.class; currentFieldName; null);
                            builder.putCustom(custom.getWriteableName(); custom);
                        } catch (NamedObjectNotFoundException ex) {
                            logger.warn("Skipping unknown custom object with type {}"; currentFieldName);
                } else if (token.isValue()) {
                    if ("version".equals(currentFieldName)) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Uninstalling X-Pack and error occurs

0.16 K 

After restarting all of my cluster nodes getting error Failed to connect to localhost port 9200: Connection refused

  0.81 K

Cannot Uninstall X Pack During Roll


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now