Hi Nur, ntpd has a 300sec limit for synchronization. If you want a more flexible NTP client, use chronyd. If you prefer to use ntpd, you should have ntpdate as a boot client and ntpd as a runtime client. When the server boots, the ntpdate client will sync time no matter the difference. As a boot client, it runs only once and exits. Then the ntpd service starts, and keep your server clock in sync with an external source. On distributions like CentOS and similar, ntpdate reads the external time sources configuration from ntpd.conf. You should need booth packages and services installed and enabled: I prefer chronyd since it does not need any extra service or procedure to keep clock synchronization. Regards, Marcos From: Nur Imam Febrianto <nur_imam(a)outlook.com&gt; Sent: terça-feira, 7 de setembro de 2021 01:08 To: oVirt Users <users(a)ovirt.org&gt; Subject: [External] : [ovirt-users] Time Drift Issues Hi All, Recently I got an warning in our cluster about time drift : Host xxxxx has time-drift of 672 seconds while maximum configured value is 300 seconds. What should I do to address this issue ? Should I reconfigure / configure ntp client on all host ? Thanks before. Regards, Nur Imam Febrianto Sent from Mail<https://urldefense.com/v3/__https:/go.microsoft.com/fwlink/?LinkI... for Windows