Error reading control group stats – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to read the control group (cgroup) statistics, usually due to insufficient permissions or incorrect configuration. This can happen in a Linux environment where Elasticsearch is running inside a Docker container. To resolve this issue, you can either disable the cgroup statistics collection by setting the ‘xpack.monitoring.collection.enabled’ to false in the Elasticsearch configuration file, or ensure that the user running Elasticsearch has the necessary permissions to read the cgroup statistics. Additionally, verify the cgroup configuration to ensure it’s correctly set up.

This guide will help you check for common problems that cause the log ” error reading control group stats ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: monitor.

Log Context

Log “error reading control group stats” classname is OsProbe.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                memoryControlGroup;
                cgroupMemoryLimitInBytes;
                cgroupMemoryUsageInBytes
            );
        } catch (final IOException e) {
            logger.debug("error reading control group stats"; e);
            return null;
        }
    }

    private static class OsProbeHolder {

 

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?