Am 13.09.21 um 14:26 schrieb richman10000...@gmail.com:
Hi,
client machines must sync only with my NTP server. the server itself
syncing with standard pools.
Today I made another vm the new NTP server.
For some reason it work on another machine. version is the same "Ver.
4.2.8p12"
here is output of the failing machine.
ntpq> peers
remote refid st t when poll reach delay offset
jitter
==============================================================================
0.debian.pool.n .POOL. 16 p - 64 0 0.000 0.000
0.000
1.debian.pool.n .POOL. 16 p - 64 0 0.000 0.000
0.000
2.debian.pool.n .POOL. 16 p - 64 0 0.000 0.000
0.000
3.debian.pool.n .POOL. 16 p - 64 0 0.000 0.000
0.000
ntpq>
I think like there is a problem with ipv6 of some sort since failing
machine is the only with IPV6 address internet . But I don't know how to
check this. For now I will use new vm.
I guess if someone will interact with this but too they will report/reopen.
It is obviously not syncing, it should look similar to this.
ntpq> peers
remote refid st t when poll reach delay offset
jitter
==============================================================================
-ec2-3-121-254-2 192.53.103.108 2 u 339 1024 77 16.953 -1.666
5.481
+mail.klausen.dk 193.67.79.202 2 u 84 1024 377 15.092 +1.568
0.580
+time.cloudflare 10.71.14.51 3 u 841 1024 377 15.649 -1.827
0.534
*time1.hs-augsbu 131.188.3.220 2 u 88 1024 377 26.345 -0.052
0.849
IPv6 only generally works fine with ntpd, although only
2.debian.pool.ntp.org is carrying IPv6 hosts. But it should sync.
Can you resolve "2.debian.pool.ntp.org" on your system (with host or
ping)? Are you sure your Port 123 is open in the outbound direction?
Bernhard
