Introduction
Chrony is an NTP client and server software designed for keeping accurate time on Linux-based systems. It is especially suited for systems that may have intermittent network connectivity or systems that need to maintain time synchronization during periods of high latency. Unlike older NTP implementations, Chrony is optimized for faster response times, greater precision, and less resource consumption.
Chrony’s main advantages include:
|
|
|
|
With Chrony, system administrators can ensure that their systems remain in sync with reliable time sources, which is crucial for everything from logging to security protocols and performance monitoring.
Chrony Commands for Systems Administrators: Installing Chrony
Before using Chrony commands, you’ll need to install Chrony on your system. This is a straightforward process.
On CentOS/RHEL/Fedora (Linux-based Distributions) |
On Ubuntu (Debian-based Distributions) |
Once Chrony is installed, you can start and enable the Chrony service.
Start and Enable Chrony |
This will start the Chrony service and ensure that it starts automatically on boot.
Key Chrony Commands for System Administrators
Checking Synchronization Status |
The first thing you need to know when working with Chrony is whether your system is synchronized to a reliable time source. To check the status, use the following command:
This command provides detailed information about the synchronization state, including the current time offset and the last time the system synchronized with its time sources.
In the example output (above), you’ll find details like:
|
|
|
Configuring Chrony Servers |
To set up Chrony to synchronize with specific NTP servers, you need to edit the /etc/chrony.conf configuration file. Open the configuration file for editing:
Inside this file, you can add or modify server entries like so:
The iburst option ensures rapid synchronization at startup. Once the changes are made, restart the Chrony service to apply them:
To verify your server synchronization status, use the following command:
Your output should look similar to (example output):
Popular Time Servers |
Here’s a list of actual time servers widely used and trusted across various network, enterprise, academic and public environments.
| # | Time Server Name | IP Address | Stratum | Description |
|---|---|---|---|---|
| 1 | pool.ntp.org | 162.159.200.123 | 1 | Public NTP server pool providing reliable time synchronization. |
| 2 | time.google.com | 216.239.35.0 | 1 | Google’s NTP servers offering high availability and accuracy. |
| 3 | time.windows.com | 131.107.0.0 | 1 | Microsoft’s public time server used for Windows devices. |
| 4 | time.apple.com | 17.253.56.24 | 1 | Apple’s public time server used by Apple devices and services. |
| 5 | time.cloudflare.com | 1.1.1.1 | 1 | Cloudflare’s fast and secure time synchronization service. |
| 6 | tick.usno.navy.mil | 192.5.41.209 | 0 | U.S. Naval Observatory’s official time server. |
| 7 | ntp1.za.net | 196.190.24.15 | 2 | South African time server operated by ZA-NTCP. |
| 8 | ntp2.nict.jp | 133.243.238.164 | 1 | National Institute of Information and Communications Technology (Japan). |
| 9 | ntp.time.org | 216.239.35.4 | 1 | Time.org’s public NTP service offering accurate time data. |
| 10 | europe.pool.ntp.org | 193.167.212.100 | 2 | European region of the public NTP server pool for global access. |
For a reliable configuration, ensure that you configure multiple time sources to avoid disruptions and ensure precision in your system clocks.
Force Synchronization |
At times, you may need to manually synchronize the system clock with a time source immediately. Use the chronyc makestep command to force synchronization and correct any clock drift.
This command is particularly useful if the system clock is off by a large margin, for instance, after the server is started or the time server has changed.
Configure Additional Time Servers |
To add more NTP servers to your Chrony configuration, edit the chrony.conf file or use the chronyc command for dynamic changes. Here’s how you can add an additional server using the chronyc CLI:
Show Synchronization Sources |
To get a more detailed view of the time sources, including reachability, stratum, and timestamps, the chronyc sourcestats command provides an in-depth summary of each server’s statistics.
Example Output:
Check Drift (Clock Stability) |
Chrony tracks the stability of the system clock with an internal drift file. Use the chronyc activity command to assess how stable your system clock is.
This command gives you insight into whether Chrony is successfully stabilizing the system clock or if there are any issues in maintaining synchronization.
View Chrony Log |
Chrony logs can provide valuable insight into any issues that may arise. On most systems, Chrony logs are stored in the system log files. To view them:
This will display recent logs related to the Chrony service. Look for errors or warnings that might indicate time synchronization issues.
Best Practices for Using Chrony
|
|
|
