> 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/frequently-asked-questions/lts3--kubelet-logs-of-all-worker-nodes-flooded-with-error-missin.md).

# LTS3- Kubelet Logs Of All Worker Nodes Flooded With Error Missing File "/etc/pf9/kube.d/pod-manifest

## Problem

In SMCP-GA freshly installed setups, the workload cluster's all the worker nodes having kubelet logs filled with errors related to Missing File "/etc/pf9/kube.d/pod-manifests".

{% tabs %}
{% tab title="Worker node- Kubelet log" %}

```javascript
Log file created at: 2023/11/06 16:26:51
Running on machine: rocky-9
Binary: Built with gc go1.19.10 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
...
I1106 16:26:51.445094    2184 kubelet.go:281] "Adding apiserver pod source"
I1106 16:26:51.445109    2184 apiserver.go:42] "Waiting for node sync before watching apiserver pods"
E1106 16:26:51.445190    2184 file.go:98] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
E1106 16:26:51.445341    2184 file_linux.go:61] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
I1106 16:26:51.446071    2184 kuberuntime_manager.go:240] "Container runtime initialized" containerRuntime="containerd" version="v1.6.8" apiVersion="v1"
W1106 16:26:51.446181    2184 reflector.go:424] vendor/k8s.io/client-go/informers/factory.go:134: failed to list *v1.Service: Get "https://10.69.90.59:443/api/v1/services?limit=500&resourceVersion=0": dial tcp 10.69.90.59:443: connect: connection refused
E1106 16:26:51.446263    2184 reflector.go:140] vendor/k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://10.69.90.59:443/api/v1/services?limit=500&resourceVersion=0": dial tcp 10.69.90.59:443: connect: connection refused
...
E1106 16:26:52.153768    2184 kubelet_node_status.go:92] "Unable to register node with API server" err="Post \"https://10.69.90.59:443/api/v1/nodes\": dial tcp 10.69.90.59:443: connect: connection refused" node="10.69.90.157"
E1106 16:26:52.252162    2184 kubelet.go:2448] "Error getting node" err="node \"10.69.90.157\" not found"
E1106 16:26:52.352702    2184 kubelet.go:2448] "Error getting node" err="node \"10.69.90.157\" not found"
...
E1106 18:36:17.028121    2184 file_linux.go:61] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
E1106 18:36:18.029016    2184 file_linux.go:61] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
E1106 18:36:19.029551    2184 file_linux.go:61] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
E1106 18:36:20.030027    2184 file_linux.go:61] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
E1106 18:36:21.030142    2184 file_linux.go:61] "Unable to read config path" err="path does not exist, ignoring" path="/etc/pf9/kube.d/pod-manifests"
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Self Managed Cloud Platform (SMCP-GA).

## Answer

This is a known issue, and will be resolved in the upcoming SMCP-5.13 release.

## Additional Information

For more details related to the release version having the fix and the ETA for release version with the fix, please open a support ticket mentioning the jira-id AIR-1257.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://platform9.com/kb/smcp/frequently-asked-questions/lts3--kubelet-logs-of-all-worker-nodes-flooded-with-error-missin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.