> 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/node-not-ready-nodelet-unable-to-start-pf9-kube.md).

# Node NotReady as Nodelet is Unable To Start PF9-Kube Due to Broken Packages

## Problem

A Cluster Node is reporting offline as *pf9-nodeletd* service is in a stopped state.

{% tabs %}
{% tab title="Nodelet Log" %}

```none
+ install_docker_engine<br>
+ remove_incompatible_packages<br>
+ apt-get -y purge docker lxc-docker docker-engine<br> E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.<br>" func=main.startKubeService file="/pf9/nodelet/nodeletd.go:210"
time="<date:time>" level=warning msg="Trying to start pf9-kube 2501. Failed task on the last run was: Configure Docker" func=main.writeExtensionData file="/pf9/nodelet/nodeletd.go:261"
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - v4.1
* Nodeletd

## Cause

The ***pf9-kube*** service was unable to purge the packages as some of the packages were broken.

{% tabs %}
{% tab title="Kube Log" %}

```none
+ install_docker_engine
+ remove_incompatible_packages
+ apt-get -y purge docker lxc-docker docker-engine
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
```

{% endtab %}
{% endtabs %}

## Resolution

1. Manually run the below command on the node to fix the broken packages.

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

```none
# sudo dpkg --configure -a
```

{% endtab %}
{% endtabs %}

2. Once this command completes successfully the *pf9-nodeletd* service will start *pf9-kube* service and the node will be reported as Ready.


---

# 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/node-not-ready-nodelet-unable-to-start-pf9-kube.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.