linux – 为什么我的ntpd不起作用?

前端之家收集整理的这篇文章主要介绍了linux – 为什么我的ntpd不起作用?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
编辑

我已经尝试了所有的建议,但似乎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’同步.

是因为偏移量太大了吗?

但是在我手动设置date by date命令后,它仍然拒绝同步到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

解决方法

啊 – 现在变得清晰了:

My machine is installed in vmware
workstation. So,form all the answers,
I guess maybe the jitter becomes so
large is because that vmware adjust
the time. I will see if I am right.

不要在VM中运行ntp.主机不保证cpu片,因此VM的时钟不准确.正如你所看到的那样,ntp正试图跟上看起来像一个异常变化的外部时钟并最终放弃的东西.

这个问题的一般答案是不运行ntp,安装VMware工具并将VM的时钟锁定到主机的时钟.

具体答案取决于您运行的Linux版本.我在CentOS上有一些注释(可能一般适用于其他RedHat系列发行版)here.

原文链接:https://www.f2er.com/linux/398625.html

猜你在找的Linux相关文章