{"id":7634,"date":"2024-05-28T21:05:03","date_gmt":"2024-05-29T04:05:03","guid":{"rendered":"https:\/\/ioflood.com\/blog\/?p=7634"},"modified":"2024-05-28T21:05:03","modified_gmt":"2024-05-29T04:05:03","slug":"install-chrony-linux","status":"publish","type":"post","link":"https:\/\/ioflood.com\/blog\/install-chrony-linux\/","title":{"rendered":"Chrony Linux Installation and Usage | Mastering Time Sync"},"content":{"rendered":"
\n
\"Command<\/figure>\n<\/div>\n

Keeping accurate time on Linux servers at IOFLOOD<\/a> is crucial for automating system operations. From our testing, we have found the Chrony command to be a useful tool for time synchronization. In today’s article, we’ll talk about this command in detail, in order to empower our bare metal cloud server<\/a> customers and fellow developers with the knowledge and tools to effectively manage time with Chrony on Linux.<\/p>\n

In this tutorial, we will guide you on how to install the chrony<\/code> command on your Linux system.<\/strong> We will show you methods for both APT and YUM-based distributions, delve into compiling chrony<\/code> from source, installing a specific version, and finally, how to use the chrony<\/code> command and ensure it’s installed correctly.<\/p>\n

So, let’s dive in and begin installing chrony<\/code> on your Linux system!<\/p>\n

TL;DR: How Do I Install and Use the ‘Chrony’ Command in Linux?<\/h2>\n

\n In most Linux distributions, you can install ‘chrony’ by running the command sudo apt-get install chrony<\/code> for Debian-based distributions like Ubuntu, or sudo yum install chrony<\/code> for RPM-based distributions like CentOS. To use ‘chrony’, you can run the command chronyc tracking<\/code> to check the synchronization status.\n<\/p><\/blockquote>\n

# For Debian-based distributions like Ubuntu\nsudo apt-get install chrony\n\n# For RPM-based distributions like CentOS\nsudo yum install chrony\n\n# To use 'chrony'\nchronyc tracking\n\n# Output:\n# Reference ID    : 123.456.789.012 (server.example.com)\n# Stratum         : 2\n# Ref time (UTC)  : Tue Apr 12 11:22:33 2022\n# System time     : 0.000000011 seconds slow of NTP time\n# Last offset     : +0.000000002 seconds\n# RMS offset      : 0.000000002 seconds\n# Frequency       : 36.042 ppm fast\n# Residual freq   : +0.000 ppm\n# Skew            : 0.001 ppm\n# Root delay      : 0.042 seconds\n# Root dispersion : 0.001 seconds\n# Update interval : 1032.1 seconds\n# Leap status     : Normal\n<\/code><\/pre>\n
This is a basic way to install and use the ‘chrony’ command in Linux, but there’s much more to learn about ‘chrony’. Continue reading for more detailed information and advanced usage scenarios.<\/p>\n
Linux Install Methods of ‘Chrony’<\/h2>\n
Chrony<\/code> is a versatile and powerful tool for managing and synchronizing the system time in Linux. It’s especially useful for systems which have intermittent internet connections, virtual machines, and systems that don’t run continuously.<\/p>\n
Installing Chrony with APT<\/h3>\n
If you’re using a Debian-based distribution like Ubuntu, you can install chrony<\/code> using the apt<\/code> package manager. Here’s how you can do it:<\/p>\n
sudo apt update\nsudo apt install chrony\n<\/code><\/pre>\n
After running these commands, your system will update the package list to ensure it has the latest versions, and then it will install chrony<\/code>.<\/p>\n
Installing Chrony with YUM<\/h3>\n
For RPM-based distributions like CentOS, you will use the yum<\/code> package manager to install chrony<\/code>. The process is similar to the apt<\/code> process:<\/p>\n
sudo yum update\nsudo yum install chrony\n<\/code><\/pre>\n
This set of commands will update your system’s package list and then install chrony<\/code>.<\/p>\n
Verifying the Installation<\/h3>\n
After installing chrony<\/code>, you should verify that it’s installed correctly. You can do this by checking the version of chrony<\/code> installed on your system:<\/p>\n
chronyd -v\n\n# Output:\n# chronyd version 3.5\n<\/code><\/pre>\n
This command will display the version of chrony<\/code> you’ve installed, confirming that the installation process was successful.<\/p>\n
Installing Chrony from Source Code<\/h2>\n
Sometimes, you might need to compile chrony<\/code> from its source code. This could be due to a variety of reasons such as the need for a specific version or the desire to customize the build process.<\/p>\n
Here’s how to install chrony<\/code> from source:<\/p>\n
# Download the source code\nwget https:\/\/download.tuxfamily.org\/chrony\/chrony-4.0.tar.gz\n\n# Extract the tarball\n tar xvf chrony-4.0.tar.gz\n\n# Change to the chrony directory\n cd chrony-4.0\/\n\n# Configure the source\n.\/configure\n\n# Compile the source code\nmake\n\n# Install chrony\nsudo make install\n<\/code><\/pre>\n
This sequence of commands downloads the source code, extracts it, configures the build process, compiles the source code, and finally installs chrony<\/code>.<\/p>\n
Installing Different Versions of Chrony<\/h2>\n
There could be several reasons you might need to install a specific version of chrony<\/code>. Different versions may have unique features, bug fixes, or compatibility with certain systems.<\/p>\n
From Source Code<\/h3>\n
To install a specific version from source, you simply need to download the tarball for that version. For example, to install version 3.5, you would replace chrony-4.0.tar.gz<\/code> in the above commands with chrony-3.5.tar.gz<\/code>.<\/p>\n
Using Package Managers<\/h3>\n
With package managers like apt<\/code> or yum<\/code>, you can also specify the version of chrony<\/code> you want to install.<\/p>\n
APT<\/h4>\n
sudo apt install chrony=3.5\n<\/code><\/pre>\n
YUM<\/h4>\n
sudo yum install chrony-3.5\n<\/code><\/pre>\n
These commands will install version 3.5 of chrony<\/code> on your system.<\/p>\n
Key Changes and Features<\/h3>\n
Different versions of chrony<\/code> come with different features and improvements. Here’s a comparison of a few versions:<\/p>\n\n\n\n\n\n\n\n
Version<\/th>\nKey Changes<\/th>\n<\/tr>\n<\/thead>\n
4.0<\/td>\nImproved NTP client, better leap second handling<\/td>\n<\/tr>\n
3.5<\/td>\nAdded support for hardware timestamping<\/td>\n<\/tr>\n
3.4<\/td>\nImproved the accuracy of the system clock<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Basic Usage of Chrony<\/h2>\n
After installing chrony<\/code>, you can use the chronyc<\/code> command to interact with the chronyd<\/code> daemon. For example, you can check the servers chrony<\/code> is synchronizing with using the sources<\/code> command:<\/p>\n
chronyc sources\n\n# Output:\n# 210 Number of sources = 4\n# MS Name\/IP address         Stratum Poll Reach LastRx Last sample\n# ===============================================================================\n# ^* time.cloudflare.com           3   6   377    36  -1582us[-1582us] +\/-   18ms\n# ^+ time.cloudflare.com           3   6   377    35  -1595us[-1595us] +\/-   18ms\n# ^+ time.cloudflare.com           3   6   377    37  -1608us[-1608us] +\/-   18ms\n# ^+ time.cloudflare.com           3   6   377    37  -1621us[-1621us] +\/-   18ms\n<\/code><\/pre>\n
This output shows that chrony<\/code> is synchronizing with four servers, all provided by Cloudflare.<\/p>\n
Verifying the Installation<\/h3>\n
You can verify that chrony<\/code> is running and synchronizing correctly by using the tracking<\/code> command:<\/p>\n
chronyc tracking\n\n# Output:\n# Reference ID    : 123.456.789.012 (server.example.com)\n# Stratum         : 2\n# Ref time (UTC)  : Tue Apr 12 11:22:33 2022\n# System time     : 0.000000011 seconds slow of NTP time\n# Last offset     : +0.000000002 seconds\n# RMS offset      : 0.000000002 seconds\n# Frequency       : 36.042 ppm fast\n# Residual freq   : +0.000 ppm\n# Skew            : 0.001 ppm\n# Root delay      : 0.042 seconds\n# Root dispersion : 0.001 seconds\n# Update interval : 1032.1 seconds\n# Leap status     : Normal\n<\/code><\/pre>\n
This output provides detailed information about the synchronization status of your system.<\/p>\n
Other Time Synchronization Methods<\/h2>\n
While chrony<\/code> is a powerful tool for time synchronization, it’s not the only option available. Another popular tool is the ntp<\/code> (Network Time Protocol) command. It’s been around for a longer time and is widely used in many systems.<\/p>\n
Installing NTP<\/h3>\n
Installing ntp<\/code> is similar to installing chrony<\/code>. Here’s how you can install it on APT and YUM-based distributions:<\/p>\n
# For Debian-based distributions like Ubuntu\nsudo apt install ntp\n\n# For RPM-based distributions like CentOS\nsudo yum install ntp\n<\/code><\/pre>\n
This will install the ntp<\/code> package on your system.<\/p>\n
Using NTP<\/h3>\n
To synchronize your system time using ntp<\/code>, you can use the ntpd<\/code> daemon. To start the ntpd<\/code> daemon, you can use the following command:<\/p>\n
sudo systemctl start ntpd\n<\/code><\/pre>\n
You can check the status of the ntpd<\/code> daemon using this command:<\/p>\n
systemctl status ntpd\n\n# Output:\n# \u25cf ntpd.service - Network Time Service\n#    Loaded: loaded (\/usr\/lib\/systemd\/system\/ntpd.service; enabled; vendor preset: disabled)\n#    Active: active (running) since Tue 2022-04-12 11:22:33 UTC; 1h 30min ago\n<\/code><\/pre>\n
This output shows that the ntpd<\/code> daemon is running.<\/p>\n
Comparing Chrony and NTP<\/h3>\n
While both chrony<\/code> and ntp<\/code> are powerful tools for time synchronization, they have their own strengths and weaknesses.<\/p>\n\n\n\n\n\n\n\n
Feature<\/th>\nChrony<\/th>\nNTP<\/th>\n<\/tr>\n<\/thead>\n
Ease of Use<\/strong><\/td>\nChrony is easier to use and configure.<\/td>\nNTP has a steeper learning curve.<\/td>\n<\/tr>\n
Resource Usage<\/strong><\/td>\nChrony uses less CPU and memory.<\/td>\nNTP uses more resources.<\/td>\n<\/tr>\n
Precision<\/strong><\/td>\nChrony offers better precision and faster synchronization.<\/td>\nNTP’s synchronization is slower and less precise.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Based on these differences, you can choose the tool that best suits your needs. If you need a tool that’s easy to use and efficient, chrony<\/code> would be the better choice. If you’re working with older systems that only support ntp<\/code>, or if you need a feature that’s only available in ntp<\/code>, then ntp<\/code> would be the better choice.<\/p>\n
Troubleshooting Issues with Chrony<\/h2>\n
While chrony<\/code> is a robust tool, you may encounter issues during installation or usage. Let’s discuss some common problems and their solutions.<\/p>\n
Issue 1: Chrony Service Not Starting<\/h3>\n
Sometimes, the chrony<\/code> service may not start after installation. You can check the status of the chrony<\/code> service using the following command:<\/p>\n
systemctl status chronyd\n\n# Output:\n# \u25cf chronyd.service - NTP client\/server\n#    Loaded: loaded (\/lib\/systemd\/system\/chronyd.service; enabled; vendor preset: enabled)\n#    Active: inactive (dead)\n<\/code><\/pre>\n
If the Active<\/code> field shows inactive (dead)<\/code>, the chrony<\/code> service isn’t running. You can start it with the following command:<\/p>\n
sudo systemctl start chronyd\n<\/code><\/pre>\n
Issue 2: Chrony Not Synchronizing with the Server<\/h3>\n
Another common issue is chrony<\/code> not synchronizing with the server. This can occur due to network issues or incorrect server configuration. You can check the synchronization status with the chronyc tracking<\/code> command. If the Leap status<\/code> field shows Not synchronised<\/code>, you’re not synchronizing with the server.<\/p>\n
To resolve this, you can try changing the server or checking your network connection.<\/p>\n
Issue 3: Chrony Installation Fails<\/h3>\n
Sometimes, the installation process might fail due to issues like package conflicts or outdated package lists. If you’re unable to install chrony<\/code> using your package manager, you can try installing it from source as discussed in the Advanced Use section.<\/p>\n
Remember, chrony<\/code> is a powerful tool, but like any tool, it requires proper configuration and usage. If you’re encountering issues, don’t hesitate to refer to the chrony<\/code> man pages or seek help from Linux communities online.<\/p>\n
Linux Time Synchronization Explained<\/h2>\n
Before diving into the practical aspects of using chrony<\/code>, it’s crucial to understand the concept of time synchronization in Linux. At its core, time synchronization is the process of coordinating system time across all devices in a network to a standard reference, usually an atomic clock.<\/p>\n
The Importance of Accurate System Time<\/h3>\n
Accurate system time is critical for many operations in a Linux system. It’s particularly vital for:<\/p>\n