high root dispersion on Windows NTP sources
This document (000019832) is provided subject to the disclaimer at the end of this document.
SUSE Manager Server for SAP 15
SUSE Manager Server 4.x
If selecting a better time source is not feasible the user may change how picky chrony is about time sources in the configuration. To do so, the
maxdistance value needs to be increased in /etc/chrony.conf to enable synchronization to a server with high root dispersion. For example an entry of:
rather than 3.0 would be high enough to tolerate the high root dispersion of a Windows server according to chrony documentation.
chronydto ignore the server for being too inaccurate in respect to upstream time sources. The
sourcescommand might show a valid measurement, but the server is not selected for synchronization. The root dispersion of a server can be viewed with the
The server might be reachable, but chrony ignores it for the purposes of time synchronization, since the high root dispersion indicates an inaccurate time source. This is usually desired behavior - chrony is rejecting inaccurate time sources based on a default heuristic. In an ideal situation chrony would skip this time server and go on to the next, hopefully better, source. However, in some deployments the only time source might be a Windows time server or AD controller on the local network, since the SLES server can't reach the outside network. This TID covers this case.
More information can be found on chrony's documentation site:
- Document ID:000019832
- Creation Date: 02-Mar-2021
- Modified Date:02-Jul-2021
- SUSE Linux Enterprise High Availability Extension
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
- SUSE Manager
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com