> 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-clock-is-not-synced-and-shows-a-node-clock-drift-issue-on-g.md).
# Node clock is not synced and shows "node clock drift" issue on GUI
## Problem
The node clock drift issue is caused due to management plane clock and node clock is not in sync with each other. Usually, this is observed through GUI as shown below:
## Environment
* Platform9 Managed Kubernetes - v5.4.0 and Higher
Scenario for the customer using local time and neither NTPD nor Chronyd. The hardware and system software clock was not synced. The hardware clock is synced with a global clock, but the timedatectl is set to use local RTC.
## Procedure
Here we are going to sync the hardware clock to the system clock
1. Check the warning by running the "timedatectl" command. Use RTC in UTC by running the below command - as the system is configured to read RTC time in local time.
{% tabs %}
{% tab title="Bash" %}
```javascript
#timedatectl set-local-rtc 0
```
{% endtab %}
{% endtabs %}
```
2. Check the timedatectl, hwclock, and system clock, then sync the hardware clock to the system clock by running:
```
{% tabs %}
{% tab title="Bash" %}
```javascript
# timedatectl
Local time: Wed 2022-11-23 10:04:53 UTC
Universal time: Wed 2022-11-23 10:04:53 UTC
RTC time: Wed 2022-11-23 09:59:46
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: n/a
# hwclock ; date
Wed 23 Nov 2022 09:55:30 AM UTC -0.860011 seconds
Wed Nov 23 10:00:36 UTC 2022
#hwclock --hctosys
```
{% endtab %}
{% endtabs %}
```
3. Verify hwclock, system clock, and timedatectl - it should be in sync now.
```
{% tabs %}
{% tab title="Bash" %}
```javascript
# hwclock ; date
Wed 23 Nov 2022 10:00:50 AM UTC -0.631062 seconds
Wed Nov 23 10:00:50 UTC 2022
#timedatectl
Local time: Wed 2022-11-23 10:00:55 UTC
Universal time: Wed 2022-11-23 10:00:55 UTC
RTC time: Wed 2022-11-23 10:00:55
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: n/a
```
{% 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 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-clock-is-not-synced-and-shows-a-node-clock-drift-issue-on-g.md?ask=&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.
