dnf install -y chrony

vi /etc/chrony.conf


# NTP Server (Tencent Cloud Internal)
server time1.tencentyun.com iburst
server time2.tencentyun.com iburst
server time3.tencentyun.com iburst
server time4.tencentyun.com iburst
server time5.tencentyun.com iburst
# Tencent Public Network NTP Server
server ntp.tencent.com iburst
server ntp1.tencent.com iburst
server ntp2.tencent.com iburst
server ntp3.tencent.com iburst
# Public NTP Server (Backup)
server cn.pool.ntp.org iburst

# NTP Server (Tencent Cloud Internal)
server time1.tencentyun.com iburst
server time2.tencentyun.com iburst
server time3.tencentyun.com iburst
server time4.tencentyun.com iburst
server time5.tencentyun.com iburst
# Tencent Public Network NTP Server
server ntp.tencent.com iburst
server ntp1.tencent.com iburst
server ntp2.tencent.com iburst
server ntp3.tencent.com iburst
# Clock Drift Log File
driftfile /var/lib/chrony/drift
# Allow Step Time Correction (Jump directly if the offset exceeds 1 second in the first 3 synchronizations)
makestep 1.0 3
# Write the System Clock Back to the Hardware Clock
rtcsync
# Obtain the TAI-UTC Offset from the System Time Zone Database
leapsectz right/UTC
# Log Directory
logdir /var/log/chrony

# Start the chronyd service.
systemctl start chronyd
# Enable autostart on boot.
systemctl enable chronyd
# Check the service status.
systemctl status chronyd
# Restart the service (after modifying the configuration)
systemctl restart chronyd

chronyc tracking

Reference ID    : A9FE0050 (169.254.0.80)
Stratum         : 3
Ref time (UTC)  : Fri Aug 21 07:08:58 2026
System time     : 0.000010930 seconds fast of NTP time
Last offset     : +0.000018760 seconds
RMS offset      : 0.000018760 seconds
Frequency       : 23.578 ppm slow
Residual freq   : -1.007 ppm
Skew            : 39.788 ppm
Root delay      : 0.001493059 seconds
Root dispersion : 0.031474017 seconds
Update interval : 2.0 seconds
Leap status     : Normal

chronyc sources -v

MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ 169.254.0.79                  2   6    77    11   +635us[ +635us] +/-   42ms
^+ 169.254.0.80                  2   6    77    11   +649us[ +649us] +/-   43ms
^+ 169.254.0.81                  2   6    77    12   +440us[ +440us] +/-   30ms
^+ 169.254.0.82                  2   6    77    11   +515us[ +515us] +/-   37ms
^* 169.254.0.83                  2   6    77    13   +640us[ +879us] +/-   42ms

chronyc sourcestats -v

chronyc activity

200 OK
10 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address

chronyc makestep

journalctl -u chronyd

timedatectl

               Local time: Fri 2026-08-21 15:14:24 CST
           Universal time: Fri 2026-08-21 07:14:24 UTC
                 RTC time: Fri 2026-08-21 07:14:24
                Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

timedatectl list-timezones | grep Asia

timedatectl set-timezone Asia/Shanghai

timedatectl set-ntp true

# 1. Confirm that chronyd is running properly.
systemctl is-active chronyd
# 2. Confirm that the system is synchronized with the NTP server (System time should be less than 1 second).
chronyc tracking | grep "System time"
# 3. Confirm that the time zone is correct.
date

# Check chronyd logs to troubleshoot network issues.
journalctl -u chronyd -n 50
# Test connectivity to the NTP server.
ping -c 4 time1.tencentyun.com
# Check whether the firewall allows UDP port 123.
firewall-cmd --list-all | grep ntp

firewall-cmd --permanent --add-service=ntp
firewall-cmd --reload

# Force synchronization immediately (use with caution on systems that require strong consistency)
chronyc makestep
# Check the offset.
chronyc tracking | grep offset

# Step the clock whenever the offset exceeds 1 second (unlimited times)
makestep 1.0 -1