How To Solve Issues Related to Log – Unable to parse vm.maxmapcount

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Jan-20

In Page Navigation (click to jump) :
Troubleshooting Background       
Related Issues  
Log Context
About Opster

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Overview

The vm.max_map_count is defined as a Long data type in Elasticsearch. 

This method in BootstrapChecks.java tries to convert it from String(Read in Sting) to the Long data type.

If you define a `vm.max_map_count` which can’t be converted to Long, then Elasticsearch throws NumberFormatException and logs below Error:

unable to parse vm.max_map_count

Troubleshooting background

To troubleshoot Elasticsearch log “Unable to parse vm.maxmapcount” it’s important to understand common problems related to Elasticsearch concepts: bootstrap checks. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Docker – ELK – vm.max_map_count 19.70 K 14

2Update max_map_count for ElasticSearch docker container Mac host 11.08 K  20


Log Context

Log ”Unable to parse vm.max_map_count [{}]” classname is BootstrapChecks.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

                 final String rawProcSysVmMaxMapCount = readProcSysVmMaxMapCount(bufferedReader);
                if (rawProcSysVmMaxMapCount != null) {
                    try {
                        return parseProcSysVmMaxMapCount(rawProcSysVmMaxMapCount);
                    } catch (final NumberFormatException e) {
                        logger.warn(() -> new ParameterizedMessage("unable to parse vm.max_map_count [{}]"; rawProcSysVmMaxMapCount); e);
                    }
                }
            } catch (final IOException e) {
                logger.warn(() -> new ParameterizedMessage("I/O exception while trying to read [{}]"; path); e);
            }






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?