Unable to obtain memory info from %s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch is unable to access the system’s memory information. This could be due to insufficient permissions, or the system not supporting the retrieval of such information. To resolve this issue, you can try running Elasticsearch with higher privileges, or check if your operating system supports memory info retrieval. If the problem persists, consider disabling the memory check by setting the ‘bootstrap.memory_lock’ to false in the Elasticsearch configuration file.

This guide will help you check for common problems that cause the log ” Unable to obtain memory info from [%s] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, memory.

Log Context

Log “Unable to obtain memory info from [%s]” classname is AutoscalingNodeInfoService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                logger.warn(() -> String.format(Locale.ROOT; "Unable to obtain processor info from [%s]"; missingNodes); e);
                    e -> {
                        logger.warn(() -> String.format(Locale.ROOT; "Unable to obtain memory info from [%s]"; missingNodes); e);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?