Hello List!
I deployed a dnsmasq installation[0] in a Docker container that is built
on top of debian and the s6-overlay software. It also contains a custom
software that reads data from a mariadb and writes the dnsmasq config files.
This software will then send the HUP signal to dnsmasq when the config
files change.
The problem will then appear one to three days later and dnsmasq will
just stop working. The process won't exit, and doesn't react to signals
anymore. Only using `kill` with SIGKILL will stop dnsmasq, which is then
restarted by s6. dnsmasq will not answer any DHCP or DNS requests in
that time.
Is that a known bug? Is this a new one? Can i somehow help
reproducing/debugging the bug? I have experience in C development, so i
can use gdb if it is required/wanted.
Best regards
- Felix "xq" Queißner
[0]
Dnsmasq version 2.85 Copyright (c) 2000-2021 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6
no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify
dumpfile
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
