Q&A
前提・実現したいこと
ここに質問の内容を詳しく書いてください。
Windows7 上の virtual boxでCentOS7のntpを有効にさせたいと考えています。
ntpの設定は済んだのですが、jitterやoffsetが大きくなりすぎて
いつまでたっても同期されません。
リスタートも何回か試しましたが、状況は改善されず。
syslogは下記のような状況です。
発生している問題・エラーメッセージ
ntp.log
ntp.log
126 Nov 11:38:12 ntpd[7344]: ntpd exiting on signal 15 226 Nov 11:38:12 ntpd[7369]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 326 Nov 11:38:12 ntpd[7369]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 426 Nov 11:38:12 ntpd[7369]: Listen and drop on 1 v6wildcard :: UDP 123 526 Nov 11:38:12 ntpd[7369]: Listen normally on 2 lo 127.0.0.1 UDP 123 626 Nov 11:38:12 ntpd[7369]: Listen normally on 3 enp0s3 172.20.241.42 UDP 123 726 Nov 11:38:12 ntpd[7369]: Listen normally on 4 docker0 172.18.0.1 UDP 123 826 Nov 11:38:12 ntpd[7369]: Listen normally on 5 lo ::1 UDP 123 926 Nov 11:38:12 ntpd[7369]: Listen normally on 6 veth33f0e9a fe80::870:b9ff:fe8d:6093 UDP 123 1026 Nov 11:38:12 ntpd[7369]: Listen normally on 7 docker0 fe80::42:eeff:fe23:51a9 UDP 123 1126 Nov 11:38:12 ntpd[7369]: Listen normally on 8 enp0s3 fe80::135a:8df1:5627:c43c UDP 123 1226 Nov 11:38:12 ntpd[7369]: Listen normally on 9 veth9224722 fe80::a0d0:70ff:fea9:f36e UDP 123 1326 Nov 11:38:12 ntpd[7369]: Listening on routing socket on fd #26 for interface updates 1426 Nov 11:38:12 ntpd[7369]: 0.0.0.0 c016 06 restart 1526 Nov 11:38:12 ntpd[7369]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM 1626 Nov 11:38:12 ntpd[7369]: 0.0.0.0 c011 01 freq_not_set 1726 Nov 11:38:21 ntpd[7369]: 0.0.0.0 c61c 0c clock_step +53.744337 s 1826 Nov 11:39:15 ntpd[7369]: 0.0.0.0 c614 04 freq_mode 1926 Nov 11:39:16 ntpd[7369]: 0.0.0.0 c618 08 no_sys_peer
該当のソースコード
ntp.conf
ntp.conf
1 2driftfile /var/lib/ntp/drift 3 4# Permit time synchronization with our time source, but do not 5# permit the source to query or modify the service on this system. 6restrict default nomodify notrap nopeer noquery 7 8# Permit all access over the loopback interface. This could 9# be tightened as well, but to do so would effect some of 10# the administrative functions. 11restrict 127.0.0.1 12restrict ::1 13 14# Hosts on local network are less restricted. 15#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap 16 17# Use public servers from the pool.ntp.org project. 18# Please consider joining the pool (http://www.pool.ntp.org/join.html). 19server xxx.xxx.xxx.xxx iburst 20#server 0.centos.pool.ntp.org iburst 21#server 1.centos.pool.ntp.org iburst 22#server 2.centos.pool.ntp.org iburst 23#server 3.centos.pool.ntp.org iburst 24 25#broadcast 192.168.1.255 autokey # broadcast server 26#broadcastclient # broadcast client 27#broadcast 224.0.1.1 autokey # multicast server 28#multicastclient 224.0.1.1 # multicast client 29#manycastserver 239.255.254.254 # manycast server 30#manycastclient 239.255.254.254 autokey # manycast client 31 32# Enable public key cryptography. 33#crypto 34 35includefile /etc/ntp/crypto/pw 36 37# Key file containing the keys and key identifiers used when operating 38# with symmetric key cryptography. 39keys /etc/ntp/keys 40 41# Specify the key identifiers which are trusted. 42#trustedkey 4 8 42 43 44# Specify the key identifier to use with the ntpdc utility. 45#requestkey 8 46 47# Specify the key identifier to use with the ntpq utility. 48#controlkey 8 49 50# Enable writing of statistics records. 51#statistics clockstats cryptostats loopstats peerstats 52 53# Disable the monitoring facility to prevent amplification attacks using ntpdc 54# monlist command when default restrict does not include the noquery flag. See 55# CVE-2013-5211 for more details. 56# Note: Monitoring will not be disabled with the limited restriction flag. 57disable monitor 58 59logfile /var/log/ntpstats/ntp.log
serverのIPアドレスはマスクしています。
ntpq -p 実行結果
ntpq
1[root@localhost wekan-backup]# ntpq -p 2 remote refid st t when poll reach delay offset jitter 3============================================================================== 4 xxxxxxxxxxxxxxx xxx.xxx.xxx.xxx 4 u 15 64 17 3.449 59904.8 43768.7 5
サーバ名と、IPアドレスはマスクしてます。offsetとjitterの値がめちゃくちゃ大きいです。
試したこと
ntpdのリスタート
firewalldの下記設定
[root@xxx ~]# firewall-cmd --add-service=ntp --permanent
success
[root@xxx ~]# firewall-cmd --reload
success
補足情報（FW/ツールのバージョンなど）
systemctl status ntp の出力結果は下記の通りです。
* ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2018-11-26 11:38:12 JST; 12min ago Process: 7368 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 7369 (ntpd) Tasks: 1 Memory: 584.0K CGroup: /system.slice/ntpd.service `-7369 /usr/sbin/ntpd -u ntp:ntp -g Nov 26 11:38:12 localhost.localdomain systemd[1]: Stopping Network Time Service... Nov 26 11:38:12 localhost.localdomain systemd[1]: Starting Network Time Service... Nov 26 11:38:12 localhost.localdomain systemd[1]: Started Network Time Service. Nov 26 11:38:12 localhost.localdomain ntpd[7369]: proto: precision = 0.032 usec Nov 26 11:38:12 localhost.localdomain ntpd[7369]: 0.0.0.0 c01d 0d kern kernel time sync enabled
回答1件
0
ベストアンサー
ntpdateで一度合わせてからntpdを立ち上げて下さい
ただしntpdがロードされているとポートが競合するのでntpdateが実行できません
かならずntpdを殺してntpdateを実行、ntpdを起動の順番です
投稿2018/11/26 03:01
総合スコア116466
あなたの回答
tips
プレビュー
バッドをするには、ログインかつ
こちらの条件を満たす必要があります。
2018/11/26 03:37 編集
2018/11/26 03:58
2018/11/26 05:18 編集
2018/11/26 05:16
2018/11/26 05:19