Linux

為什麼我的 ntpd 不起作用?

  • April 22, 2021

編輯

我已經嘗試了你所有的建議,但似乎 ntpd 只是拒絕同步到伺服器。

[vivs@peter-centos ~]$ /usr/sbin/ntpq -np
    remote           refid      st t when poll reach   delay   offset  jitter
==============================================================
192.168.0.30    .LOCL.           1 u   11   64    3    0.984  232732. 20083.2

這個抖動“20083.2”是否表示手動更改時間?

我已經關閉了 vmware 的時間同步。

原始問題

這是ntp的狀態

[root@peter-centos gw]# /usr/sbin/ntpq -pn
remote           refid      st t when poll reach   delay   offset  jitter
=============================================
192.168.0.30    .LOCL.           1 u  153 1024  377    0.950  1905553 274023.
*127.127.1.0     .LOCL.          10 l    9   64  377    0.000    0.000   0.001

您可以看到它只與本地時鐘“127.127.1.0”同步。

是不是因為偏移量太大?

但是我手動設置日期命令後,還是拒絕同步到192.168.0.30

這可能是 ntp.conf

# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery

# Permit all access over the loopback interface.  This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
restrict -6 ::1

# Hosts on local network are less restricted.
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
#server 0.centos.pool.ntp.org
#server 1.centos.pool.ntp.org
#server 2.centos.pool.ntp.org
server 192.168.0.30 #blf
#broadcast 192.168.1.255 key 42         # broadcast server
#broadcastclient                        # broadcast client
#broadcast 224.0.1.1 key 42             # multicast server
#multicastclient 224.0.1.1              # multicast client
#manycastserver 239.255.254.254         # manycast server
#manycastclient 239.255.254.254 key 42  # manycast client

# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available.
#server 127.127.1.0     # local clock
#fudge  127.127.1.0 stratum 10

# Drift file.  Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /var/lib/ntp/drift

# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography.
keys /etc/ntp/keys

# Specify the key identifiers which are trusted.
#trustedkey 4 8 42

# Specify the key identifier to use with the ntpdc utility.
#requestkey 8

# Specify the key identifier to use with the ntpq utility.
#controlkey 8
lkey 8
h the ntpdc utility.
#requestkey 8

# Specify the key identifier to use with the ntpq utility.
#controlkey 8
lkey 8
olkey 8
lkey 8

**2021 年 4 月更新:**至少從 2016 年開始,正確的答案是在 VM 中執行 NTP。下面的答案應該被棄用。

之前:

啊——現在很清楚了:

我的機器安裝在 vmware 工作站中。所以,從所有的答案來看,我猜可能抖動變得如此之大是因為 vmware 調整了時間。我會看看我是否正確。

不要在虛擬機中執行 ntp。主機不保證 CPU 片,因此 VM 的時鐘不准確。正如你所看到的,ntp 正試圖跟上它看起來像一個變化很大的外部時鐘並最終放棄。

這個問題的一般答案是不執行 ntp,安裝 VMware 工具並將 VM 的時鐘鎖定到主機的時鐘。

具體答案取決於您執行的 Linux 版本。我在這裡有一些關於 CentOS(可能普遍適用於其他 RedHat 系列發行版)的註釋

引用自:https://serverfault.com/questions/95655