Carlos E. R. wrote:
El 2020-09-09 a las 17:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Yes, and it replaces non reachable IPv6 servers with other IPv6 servers, which it can know before trying that they will not work.
Is that a problem? chrony works fine here, ipv4-only vanilla config on Tumbleweed.
Yes, IMO what happens is a problem.
Then the next step is one of two -
or the chrony mailing list:
chrony-users@chrony.tuxfamily.org
Yes, I was thinking of that, but I will loose access to that machine soon. Unless I switch some of my machines to chronyd.
That is very easy to do, you can switch back and forth between ntp and chrony with two commands. systemctl disable --now ntpd systemctl enable --now chrony Go back to ntp: systemctl disable --now chrony systemctl enable --now ntpd
It is now 21:04 hours, and the log is silent, which means it has a correct source.
Actually, 'chronyc sources' will tell you that, not the log.
When it uses IPv6 addresses, every half hour it tries another, because it does not work.
That is an assumption - it probably works very well, but chrony might be looking for a better time source. (my guess). I still find it interesting that I cannot reproduce the behaviour. Have you enabled more verbose logging or something like that? -- Per Jessen, Zürich (17.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org