> 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/generic/how-to/hostagent-logs-shows-cert-update-thread-is-waiting-with-timeout.md).

# Hostagent Logs Shows "Cert Update Thread Is Waiting With Timeout of 24 Hours"

## Problem

Node doesn't converge to the Platform9 Management Plane. ***Hostagent*** logs show entries like below every 24 hours. However, nodes remain in a disconnected state on the PMK GUI.

{% tabs %}
{% tab title="Hostagent Logs" %}

```javascript
2023-05-26 09:53:33,101 - cert_update_thread.py INFO - CA list returned by vouch is subset of CAs on host. No CA update needed.
2023-05-26 09:53:33,103 - cert_update_thread.py INFO - Cert Update thread is now waiting on an event with timeout of 24 hours
2023-05-27 09:53:37,102 - cert_update_thread.py INFO - CA list returned by vouch is subset of CAs on host. No CA update needed.
2023-05-27 09:53:37,105 - cert_update_thread.py INFO - Cert Update thread is now waiting on an event with timeout of 24 hours
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - v5.6.4 and Higher.

## Cause

* The issue happens due to the node clock is not in sync.

```javascript
$ timedatectl
      Local time: Wed 2023-06-07 10:02:28 UTC
  Universal time: Wed 2023-06-07 10:02:28 UTC
        RTC time: Wed 2023-06-07 09:59:17
       Time zone: UTC (UTC, +0000)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: n/a
```

## Resolution

* Sync the node clock using ***timedatectl*** and ***hwclock*** command followed by ***pf9-hostagent*** service restart.

{% tabs %}
{% tab title="Sync clock using below command" %}

```javascript
$ sudo hwclock --hctosys
```

{% endtab %}
{% endtabs %}

* Verify if clock is synced.

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

```javascript
$ timedatectl
      Local time: Wed 2023-06-07 10:28:46 UTC
  Universal time: Wed 2023-06-07 10:28:46 UTC
        RTC time: Wed 2023-06-07 10:28:46
       Time zone: UTC (UTC, +0000)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: n/a
```

{% endtab %}
{% endtabs %}

* Restart the ***pf9-hostagent*** service.

{% tabs %}
{% tab title="Pf9-hostagent service" %}

```javascript
$ sudo systemctl restart pf9-hostagent
```

{% endtab %}
{% endtabs %}

* Verify if the service is running and the node started converging to the management plane. GUI should show the node as connected.


---

# 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/generic/how-to/hostagent-logs-shows-cert-update-thread-is-waiting-with-timeout.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.