Re: Repeated 'refresh'es may cause excessive DNS queries
Matt Rude <matt-5MXZ7I6++7MvAsz/[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Organization | The Odin Network |
| Message-ID | <[email protected]> |
Tim- What happens if you add '-4' to your Chrony process? Looking at the logs, it appears your system is unable to connect to an IPv6 address. After it tries several times, it finds a IPv4 address and syncs. This may be a problem with your docker setup or host system, regardless adding the '-4' flag should prevent Chrony from trying the IPv6 address. Cheers -Matt On 3/12/2024 11:35 AM, [email protected] wrote: >> That seems to be working for me as expected. I see one request per >> refresh. Can you please build chronyd with --enable-debug and post the >> chronyd -dd output for first few refresh commands? > > I have attached the debug log after 4 refresh commands. > chrony made about 320 DNS requests after those. > > I built chrony at commit ad37c409c9170a5f4e2ee6068f49fcd0911b3215. > > Regards, > Tim > > -- Matt Rude | The Odin Network | Minneapolis, Minnesota, USA Email : matt-5MXZ7I6++7MvAsz/[email protected] | PGP Key : 0x77334881C84C2599 -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]