Hi Dominik, On Sun, Aug 25, 2024 at 2:51 PM Dominik Derigs via Dnsmasq-discuss < dnsmasq-discuss@lists.thekelleys.org.uk> wrote:
> Many possibilities and the more we know, the better. I really doubt there > is anything systematic concerning dnsmasq in docker but rather something > related to the particular container or the particular configuration. > My bad - I didn't mention, that the container worked just fine for months until we completed the migration and put it under full load. So this freezing issue happens only under significant load (so perhaps it's some race condition), e.g. this is our stats for 4 hours: dnsmasq: time 1724557801 dnsmasq: cache size 150, 0/711 cache insertions re-used unexpired cache entries. dnsmasq: queries forwarded 4744, queries answered locally 3823 dnsmasq: queries for authoritative zones 0 dnsmasq: DNSSEC per-query subqueries HWM 0 dnsmasq: DNSSEC per-query crypto work HWM 0 dnsmasq: DNSSEC per-RRSet signature fails HWM 0 dnsmasq: pool memory in use 672, max 1248, allocated 2400 dnsmasq: child processes for TCP requests: in use 0, highest since last SIGUSR1 0, max allowed 20. dnsmasq: server X.X.X.X#53: queries sent 4160, retried 3, failed 0, nxdomain replies 196, avg. latency 2ms dnsmasq: server X.X.X.X#53: queries sent 2412, retried 2, failed 0, nxdomain replies 72, avg. latency 4ms Sincerely, Danil Smirnov > > Best, > Dominik > > > >Am 25. August 2024 12:21:27 MESZ schrieb Dimitry Andric < > dimi...@unified-streaming.com>: > >>On 25 Aug 2024, at 11:07, Danil Smirnov <danil.smir...@gmail.com> wrote: > >>> > >>> There is some evidence on the Internet that dnsmasq doesn't play well > with Docker (when run in a Docker container), i.e.: > >>> > >>> > https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q4/015909.html > >>> > https://www.reddit.com/r/homelab/comments/1d7w3l9/struggling_to_diagnose_irregular_hangs_with/ > >>> https://github.com/dockur/dnsmasq/issues/7 > >>> > >>> I have also faced the same issue - after some hours/days, dnsmasq > becomes irresponsive and can't be fixed by e.g. docker kill > --signal=SIGHUP, but only by the container restart. Memory consumption > didn't grow and no errors/warnings were found in the logs. > >>> > >>> Are there any suspects we can consider and start checking how to fix? > >> > >>Has anybody ever attached a debugger to such a hanging instance? Or at > the least run an strace on it? > >> > >>Because without more information it is very unlikely that the root cause > will be found. > >> > >>-Dimitry > >> > >> > >>_______________________________________________ > >>Dnsmasq-discuss mailing list > >>Dnsmasq-discuss@lists.thekelleys.org.uk > >>https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
