# Dynatrace cluster nodes clock out of sync

**URL:** <https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672>\
**Category:** Dynatrace Managed\
**Tags:** dynatrace-managed, cluster-management-console\
**Created:** [May 10, 2023, 10:17pm UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672 "2023-05-10T22:17:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dtdeer](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@dtdeer](https://community.dynatrace.com/u/dtdeer)\
**Post date:** [May 10, 2023, 10:17pm UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/1 "2023-05-10T22:17:09Z")

</div>

I go the warning like “Server time of server1 is out of symnc. … Please enable NTP on all cluster nodes.” According to this post,&nbsp;[https://community.dynatrace.com/t5/Open-Q-A/time-sync/m-p/112956/highlight/true#M8618,](https://community.dynatrace.com/post/112956)&nbsp;“It’s important to have NTP setup correctly on those hosts. Otherwise OneAgents will be synced with the wrong time and will produce PurePaths that might be off (in the future).”

But how do I set up NTP? I thought NTP comes with Casssandra. I checked NTP service on cluster nodes and it appeared as not installed.

++  
$ nptstat  
bash: nptstat: command not found…  
$ systemctl status ntpd  
Unit ntpd.service could not be found.  
++

Any suggestions?

---

<div class="post-metadata">

**Author:** ![Yann\_Buccellato](https://avatars.discourse-cdn.com/v4/letter/y/97f17d/32.png) [@Yann\_Buccellato](https://community.dynatrace.com/u/Yann_Buccellato)\
**Post date:** [May 11, 2023, 10:50am UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/2 "2023-05-11T10:50:35Z")

</div>

NTP doesn’t depend on Dynatrace itself.

You or the Admin of the system that you are working on should set up NTP on Virtual Machine itself and the configuration of the NTP should reference a central NTP serves that keeps track of the current time.

You should definitely speak with one of your Org. Admins and he’ll probably have the solution for you

---

<div class="post-metadata">

**Author:** ![dtdeer](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@dtdeer](https://community.dynatrace.com/u/dtdeer)\
**Post date:** [May 11, 2023, 5:50pm UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/3 "2023-05-11T17:50:18Z")

</div>

y\_buccellato,

Thanks for the quick response. I have two more questions:

1. Should I set up NTP service on ActiveGate nodes too?

2. Between ntpd and chronyd, which one works better with Dynatrace, or which one is a better choice generally?

Regards,

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [May 14, 2023, 6:43pm UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/4 "2023-05-14T18:43:16Z")

</div>

1. Not necessarily, but I highly recommend having NTP on each host. Even hosts not related to Dynatrace.
2. Both will work fine, probably Chrony would be a preferred choice in recent Linux distributions.

---

<div class="post-metadata">

**Author:** ![dtdeer](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@dtdeer](https://community.dynatrace.com/u/dtdeer)\
**Post date:** [May 16, 2023, 3:38am UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/5 "2023-05-16T03:38:50Z")

</div>

Julius\_Loman,

Thank you. I made sure chronyd running on all cluster hosts and activegates.

Regards

---

<div class="post-metadata">

**Author:** ![elsplunko](https://avatars.discourse-cdn.com/v4/letter/e/e56c9b/32.png) [@elsplunko](https://community.dynatrace.com/u/elsplunko)\
**Post date:** [August 14, 2023, 12:43pm UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/6 "2023-08-14T12:43:32Z")

</div>

In this regard it would be nice to implement an option besides /etc/ntp.conf to also choose /etc/chrony.conf or in this regard any other path?

Is there already something planned as chrony is the new standard 🙂

---

<div class="post-metadata">

**Author:** ![dtdeer](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@dtdeer](https://community.dynatrace.com/u/dtdeer)\
**Post date:** [August 14, 2023, 5:28pm UTC](https://community.dynatrace.com/t/dynatrace-cluster-nodes-clock-out-of-sync/39672/7 "2023-08-14T17:28:03Z")

</div>

As far as I know, Chrony is the default NTP for Oracle Linux. Chrony is also the standard NTP used by my organization.
