CentOS chrony # Не синхронизируется
Я установил CentOS и chrony:
CentOS Linux release 7.9.2009 (Core)
chronyc (chrony) version 3.4 (+READLINE +SECHASH +IPV6 +DEBUG)
Но chronyc не синхронизируется, он показывает "Не синхронизирован" с онлайн-серверами:
Stratum : 0
Ref time (UTC) : Thu Jan 01 00:00:00 1970
System time : 0.000000022 seconds fast of NTP time
Last offset : +0.000000000 seconds
RMS offset : 0.000000000 seconds
Frequency : 7.485 ppm fast
Residual freq : +0.000 ppm
Skew : 0.000 ppm
Root delay : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised
$ chronyc activity
200 OK
4 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 sources
210 Number of sources = 4
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^? ntp1.time.nl 0 7 0 - +0ns[ +0ns] +/- 0ns
^? srv102.gosix.net 0 7 0 - +0ns[ +0ns] +/- 0ns
^? 95.211.160.148 0 7 0 - +0ns[ +0ns] +/- 0ns
^? 108.61.164.200.vultr.com 0 7 0 - +0ns[ +0ns] +/- 0ns
Я проверил системы, но не исправил :(
- Сервис UP, прослушивание и отсутствие правил FW:
Redirecting to /bin/systemctl status chronyd.service
● chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-09-14 14:00:06 UTC; 30min ago
Docs: man:chronyd(8)
man:chrony.conf(5)
Process: 20112 ExecStartPost=/usr/libexec/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
Process: 20108 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 20110 (chronyd)
CGroup: /system.slice/chronyd.service
└─20110 /usr/sbin/chronyd
udp UNCONN 0 0 127.0.0.1:323 *:*
udp UNCONN 0 0 [::1]:323 [::]:*
$ firewall-cmd --state
not running
- Есть связность (я думаю):
$ sudo tcpdump -n -i eth0 host x.x.x.x and port 123
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
14:50:01.271828 IP x.x.x.x.59970 > 37.97.195.195.ntp: NTPv4, Client, length 48
14:50:06.349541 IP x.x.x.x.47580 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:06.552169 IP x.x.x.x.47466 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:06.754817 IP x.x.x.x.58556 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:06.955328 IP x.x.x.x.51318 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:08.361636 IP x.x.x.x.41164 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:08.589598 IP x.x.x.x.56413 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:08.791262 IP x.x.x.x.49022 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:08.991537 IP x.x.x.x.46726 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:10.387966 IP x.x.x.x.51796 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:10.593499 IP x.x.x.x.46951 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:10.818528 IP x.x.x.x.54258 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:11.023718 IP x.x.x.x.35249 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:12.415437 IP x.x.x.x.41217 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:12.620785 IP x.x.x.x.35431 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:12.820703 IP x.x.x.x.49821 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:13.045280 IP x.x.x.x.33577 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:14.429182 IP x.x.x.x.36668 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:14.644413 IP x.x.x.x.57601 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:14.844912 IP x.x.x.x.58888 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:15.063969 IP x.x.x.x.48123 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:16.456308 IP x.x.x.x.52534 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:16.658906 IP x.x.x.x.55923 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:16.877854 IP x.x.x.x.52645 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:17.088974 IP x.x.x.x.56502 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:18.474940 IP x.x.x.x.43092 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:18.690837 IP x.x.x.x.47503 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:18.891465 IP x.x.x.x.56651 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:19.115303 IP x.x.x.x.52604 > 108.61.164.200.ntp: NTPv4, Client, length 48
14:50:20.497304 IP x.x.x.x.46100 > 94.198.159.10.ntp: NTPv4, Client, length 48
14:50:20.724585 IP x.x.x.x.53853 > 95.211.160.148.ntp: NTPv4, Client, length 48
14:50:20.926573 IP x.x.x.x.55653 > 5.145.135.89.ntp: NTPv4, Client, length 48
14:50:21.126817 IP x.x.x.x.42011 > 108.61.164.200.ntp: NTPv4, Client, length 48
^C
33 packets captured
33 packets received by filter
0 packets dropped by kernel
$ nc -zvu 95.211.160.148 123
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 95.211.160.148:123.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.01 seconds.
- Я добавил ntp-сервер в /etc/chrony.conf, который, как я знаю, работает / подключается, но он не работал ...
Любая идея?
С Уважением!.