> 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/smcp/solution/kubelet-service-is-unstable-due-to-invalid-vm-overcommit-memory.md).

# Kubelet Service is Unstable due to Invalid vm/Overcommit\_memory Kernel Flag

## Problem

* *kubelet* service is unstable showing the below error in the log:

{% tabs %}
{% tab title="Kubelet log" %}

```javascript
Failed to start ContainerManager invalid kernel flag: vm/overcommit_memory, expected value: 1, actual value: 0
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Edge Cloud v-5.3.0

## Cause

* In one of the master node, the vm.overcommit\_memory parameter in the /etc/sysctl.conf file set to "0"

{% tabs %}
{% tab title="/etc/sysctl.conf" %}

```javascript
#sysctl vm.overcommit_memory

vm.overcommit_memory = 0
```

{% endtab %}
{% endtabs %}

## Resolution

* Replace the value of above parameter in the /etc/sysctl.conffile with 1

{% tabs %}
{% tab title="Terminal" %}

```bash
# overcommit memory

vm.overcommit_memory=0 >>>>>>>>>>>>>> Replace this with 1
```

{% endtab %}
{% endtabs %}

* Run below command to persist the change made above:

{% tabs %}
{% tab title="Terminal" %}

```bash
# sysctl -p
```

{% endtab %}
{% endtabs %}

* After making the change, confirm if the value is reflected for the parameter:

{% tabs %}
{% tab title="Terminal" %}

```bash
# sysctl vm.overcommit_memory
```

{% endtab %}
{% endtabs %}

* Check pf9-kubelet.service status, if it is still stuck in failed state, restart once and confirm if it becomes healthy.

{% tabs %}
{% tab title="Terminal" %}

```javascript
# systemctl status pf9-kubelet
# systemctl restart pf9-kubelet
```

{% endtab %}
{% endtabs %}


---

# 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 dynamically 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/smcp/solution/kubelet-service-is-unstable-due-to-invalid-vm-overcommit-memory.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 `build a script that syncs our docs to a CMS` 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.