> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/solutions/centos-nodes-fluctuating-between-ready-and-notready-states.md).

# Nodes Fluctuating Between Ready and NotReady State Due to Kernel Memory Leak Issue

## Problem

* The Red Hat / CentOS nodes in our cluster are fluctuating between `Ready` and `NotReady` states.
* SSH terminal is frozen when running any linux commands. Below error message is observed in the system logs when system hits this bug.

{% tabs %}
{% tab title="/var/log/messages" %}

```bash
kernel: XFS: 6(238873) possible memory allocation deadlock size 144 in kmem_alloc (mode:0x8250)
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - All Versions
* Red Hat / CentOS 7 with kernel < 3.10.0-1075.el7

## Answer

* This happens due to a known Red Hat / CentOS 7.6 memory leak issue and can be resolved by adding `cgroup.memory=nokmem` to the GRUB configuration.
* Please engage the System Admin for adding above parameter in GRUB. If the issue persists, please reach out to the respective community or the OS support.

## Additional Information

* Refer below link for more details on the issue.
  * [slab leak causing a crash when using kmem control group](https://bugzilla.redhat.com/show_bug.cgi?id=1507149#c134)
  * [Docker fails to start containers with cgroup memory allocation error](https://github.com/docker/for-linux/issues/841#issuecomment-583263198)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/solutions/centos-nodes-fluctuating-between-ready-and-notready-states.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
