Learning about time synchronization with chrony and NTP
119
As we can see, we know what the status is for each server based on the first column (Mas outlined here ^: This is a server =:
This is a peerIn the second column (S, we can seethe different statuses for each entry, as follows *: This is our current synchronized server +: This is another acceptable time source ?: This is used to indicate sources that have lost network connectivity x This server is considered a false ticker (its time is considered inconsistent compared to other sources
: A source that has a high variability (it also appears during daemon startup)
So, we can see that our system is connected to a server that is considering the reference at ts1.sct.de, which is a stratum 2 server.
More detailed information can be checked via
the chronyc tracking command, as illustrated in the following screenshot:
Figure 4.6 – chronyc tracking output
Tools for Regular Operations
120
This provides more detailed information about our clock and our reference clock. Each field in the preceding screenshot has the following meaning Reference ID ID and name/
Internet Protocol (
IP) address of the server that the system has synchronized Stratum Our stratum level. In this example, our synchronized server is a stratum 3 clock Ref time (UTC The last time the reference was processed System time When running in normal mode (without time skip, this references how faraway or behind the system is from the reference clock Last offset Estimated offset on the last clock update. If it’s
positive, this indicates that our local time was ahead of our source RMS offset
Long-term average (
LTA) of the offset value Frequency This is the rate at which the system clock would be wrong if chronyd does not fix it, expressed in
Share with your friends: