Hi mixmastamyk,
Would you be able to provide the following information:
* dpkg --get-selections | cut -f 1 * /etc/resolv.conf * /etc/NetworkManager/NetworkManager.conf * /etc/dnsmasq.conf * /run/dnsmasq/resolv.conf * /var/run/dhcpd.leases (or /run/dhcpd.leases?)
Do make sure you remove any sensitive information from those.
Also, when your system hits the 100% issue, could you provide the following info:
* ps aux - Is logrotate running? (Or some other 'heavy' process?) * journalctl -f - Any mention of "maximum number of concurrent dns queries reached"?
https://github.com/jedisct1/dnsblast provides a tool which could be used to try to reproduce the issue.
@sefs:
Your issue may be unrelated to mixmastamyk's bug. Wouldyou be able to file a separate bug providing the same information I just requested to mixmastamyk above?
Thanks!
Hi mixmastamyk,
Would you be able to provide the following information:
* dpkg --get-selections | cut -f 1 ager/NetworkMan ager.conf resolv. conf dhcpd.leases (or /run/dhcpd.leases?)
* /etc/resolv.conf
* /etc/NetworkMan
* /etc/dnsmasq.conf
* /run/dnsmasq/
* /var/run/
Do make sure you remove any sensitive information from those.
Also, when your system hits the 100% issue, could you provide the following info:
* ps aux
- Is logrotate running? (Or some other 'heavy' process?)
* journalctl -f
- Any mention of "maximum number of concurrent dns queries reached"?
https:/ /github. com/jedisct1/ dnsblast provides a tool which could be used to try to reproduce the issue.
@sefs:
Your issue may be unrelated to mixmastamyk's bug. Wouldyou be able to file a separate bug providing the same information I just requested to mixmastamyk above?
Thanks!