<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Dynatrace cluster nodes clock out of sync in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/220620#M2750</link>
    <description>&lt;P&gt;As far as I know, Chrony is the default NTP for Oracle Linux. Chrony is also the standard NTP used by my organization.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Aug 2023 17:28:03 GMT</pubDate>
    <dc:creator>dtdeer</dc:creator>
    <dc:date>2023-08-14T17:28:03Z</dc:date>
    <item>
      <title>Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/211839#M2515</link>
      <description>&lt;P&gt;I go the warning like "Server time of server1 is out of symnc. ... Please enable NTP on all cluster nodes." According to this post,&amp;nbsp;&lt;A href="https://community.dynatrace.com/t5/Open-Q-A/time-sync/m-p/112956/highlight/true#M8618," target="_blank" rel="noopener"&gt;https://community.dynatrace.com/t5/Open-Q-A/time-sync/m-p/112956/highlight/true#M8618,&lt;/A&gt;&amp;nbsp;"&lt;SPAN&gt;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)."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;++&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;$ nptstat&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;bash: nptstat: command not found...&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;$ systemctl status ntpd&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Unit ntpd.service could not be found.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;++&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2023 06:51:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/211839#M2515</guid>
      <dc:creator>dtdeer</dc:creator>
      <dc:date>2023-05-11T06:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/211883#M2516</link>
      <description>&lt;P&gt;NTP doesn't depend on Dynatrace itself.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;You should definitely speak with one of your Org. Admins and he'll probably have the solution for you&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2023 10:50:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/211883#M2516</guid>
      <dc:creator>y_buccellato</dc:creator>
      <dc:date>2023-05-11T10:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/211963#M2517</link>
      <description>&lt;P&gt;y_buccellato,&lt;/P&gt;&lt;P&gt;Thanks for the quick response. I have two more questions:&lt;/P&gt;&lt;P&gt;1. Should I set up NTP service on ActiveGate nodes too?&lt;/P&gt;&lt;P&gt;2. Between ntpd and chronyd, which one works better with Dynatrace, or which one is a better choice generally?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2023 17:50:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/211963#M2517</guid>
      <dc:creator>dtdeer</dc:creator>
      <dc:date>2023-05-11T17:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/212167#M2518</link>
      <description>&lt;OL&gt;&lt;LI&gt;Not necessarily, but I highly recommend having NTP on each host. Even hosts not related to Dynatrace.&lt;/LI&gt;&lt;LI&gt;Both will work fine, probably Chrony would be a preferred choice in recent Linux distributions.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 14 May 2023 18:43:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/212167#M2518</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2023-05-14T18:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/212301#M2519</link>
      <description>&lt;P&gt;Julius_Loman,&lt;/P&gt;&lt;P&gt;Thank you. I made sure chronyd running on all cluster hosts and activegates.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 16 May 2023 03:38:50 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/212301#M2519</guid>
      <dc:creator>dtdeer</dc:creator>
      <dc:date>2023-05-16T03:38:50Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/220589#M2749</link>
      <description>&lt;P&gt;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?&lt;BR /&gt;&lt;BR /&gt;Is there already something planned as chrony is the new standard &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 12:43:32 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/220589#M2749</guid>
      <dc:creator>elsplunko</dc:creator>
      <dc:date>2023-08-14T12:43:32Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace cluster nodes clock out of sync</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/220620#M2750</link>
      <description>&lt;P&gt;As far as I know, Chrony is the default NTP for Oracle Linux. Chrony is also the standard NTP used by my organization.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 17:28:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-cluster-nodes-clock-out-of-sync/m-p/220620#M2750</guid>
      <dc:creator>dtdeer</dc:creator>
      <dc:date>2023-08-14T17:28:03Z</dc:date>
    </item>
  </channel>
</rss>

