记⼀次chrony同步失败问题排查先简单介绍⼀下chrony
实际配置中总是出现各种问题,排除时,⾸先关闭selinux,关闭防⽕墙。
读取配置文件失败尝试过多次,最近⼀次成功的案例是,服务端的配置⽂件修改了三项
⾃⼰是⾃⼰的服务器
开启同步许可
# Allow NTP client access from local network.
allow 192.168.102.0/24
开启同步层
耀的拼音# Serve time even if not synchronized to a time source.
local stratum 10
含有服务端和客户端:服务名为 chronyd,客户端⼯具chronyc
配置⽂件 /f
黄晓娟简历此项为时间源地址
修改后需要重启服务,然后⽤chronyc sources -v 查看同步情况
[root@student ~]# chronyc sources -v
210 Number of sources = 1
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| / '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
个性签名大全2013最新版的超拽|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
=============================================================================== ^? 192.168.102.131 0 8 0 - +0ns[ +0ns] +/- 0ns
这是服务器不可达,时间未同步的反馈
[root@student ~]# chronyc sources -v
210 Number of sources = 1
曼哈顿追逐.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| / '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted offset,
|| Log2(Polling interval) --. | | yyyy = measured offset,
|| \ | | zzzz = estimated error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample刀剑封魔录任务攻略
=============================================================================== ^* 192.168.102.131 3 6 17 13 +5813ns[ +120us] +/- 41ms
这是正常同步的信息反馈
理论上,只要服务安装了,配置⽂件没错,重启过服务,关闭了selinux和firewalld,⽹络通,就会很对进⾏同步,此次却⽆法进⾏同步。结果发现是客户端的chrony版本⽐服务端的chrony版本⾼导致,
全部更新到最新版本后马上就同步了
发布评论