Carlos E. R. wrote:
El 2020-09-09 a las 15:20 +0200, Per Jessen escribió:
Carlos E. R. wrote:
El 2020-09-09 a las 12:38 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Hi Dave,
I have not seen Carlos describe any actual problem in chrony. That chrony attempts to contact IPv6 addresses is fine, it does not upset the function.
That is not known for certain, only assumed.
I have not seen anything that suggests otherwise. Running chrony on my TW test-system works fine, ipv4-only. Hasn't tried an ipv6 address yet though. (using 2.pool.opensuse).
But I pasted my log, it showed problems:
I don't see any problems in what you posted. You also later posted output from "chronyc tracking", saying clearly it works fine.
No, you are confused. At that point I had already disabled IPv6 in sysconfig/chronyd.
Maybe you can post something that shows how it is _not_ working ? IMO, the log does not show any problems.
The log you posted looks like normal operations to me. The chrony faq says "The clients [chronies] will automatically replace the servers when they become unreachable, or otherwise unsuitable for synchronisation, with new servers from the pool."
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. -- Per Jessen, Zürich (24.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org