Skip to main content

Step-by-Step Guide to Installing Chrony on Linux 8

Step-by-Step Guide to Installing Chrony on Linux 8





Chrony is a time synchronization tool for Linux 8 that ensures accurate and consistent timekeeping across networked devices. It surpasses the conventional Network Time Protocol (NTP) by mitigating network delay variations, resulting in superior accuracy. Chrony is particularly useful in cloud environments where IP addresses can change dynamically, ensuring smooth transitions without abrupt time shifts. By leveraging hardware timestamping and innovative features, Chrony optimizes time synchronization, enhancing the reliability and efficiency of your system.

In this article, I will provide a, step-by-step walkthrough for installing Chrony on a Linux 8 system, empowering you to enhance time synchronization in your environment. 

Prerequisites:


A Linux 8 system (e.g., CentOS 8, RHEL 8).
Administrative privileges (sudo or root access).

Step 1: Update Package Repositories:


Open a terminal.
Update the package repositories using the following command:

sudo dnf update

Step 2: Install Chrony:


In the same terminal, install Chrony using the following command:

sudo dnf install chrony

Step 3: Enable and Start Chrony:


Once installed, enable the Chrony service to start on boot:

sudo systemctl enable chronyd

Start the Chrony service for the current session:

sudo systemctl start chronyd


Step 4: Verify Chrony Status:


Check the status of the Chrony service to ensure it's active and running without errors:

sudo systemctl status chronyd

Step 5: Configure Chrony:


Open the Chrony configuration file using a text editor (e.g., nano or vi):

sudo vi  /etc/chrony.conf

Configure the NTP servers by adding server entries under the "Server" section. For example:

server time.example.com iburst
Replace "time.example.com" with the NTP server of your choice.

Example: server 169.254.169.254 iburst

Save and close the configuration file.

Step 6: Restart Chrony:


Restart the Chrony service to apply the configuration changes:

sudo systemctl restart chronyd

Step 7: Initial Synchronization:


Wait for a few minutes to allow Chrony to synchronize with the NTP servers.
Verify synchronization status by running:

chronyc tracking

[root@ocicliserver etc]# chronyc tracking
Reference ID    : A9FEA9FE (169.254.169.254)
Stratum         : 3
Ref time (UTC)  : Fri Aug 25 15:39:02 2023
System time     : 0.000007874 seconds fast of NTP time
Last offset     : +0.000008260 seconds
RMS offset      : 0.000056723 seconds
Frequency       : 13.192 ppm slow
Residual freq   : +0.048 ppm
Skew            : 0.008 ppm
Root delay      : 0.001442775 seconds
Root dispersion : 0.018755877 seconds
Update interval : 1033.6 seconds
Leap status     : Normal

Step 8: Check Source from where it is synced


chronyc sources 


MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* 169.254.169.254               2  10   377   997   -500us[ -492us] +/-   18ms






If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...
Post a Comment
Read more