[Bug 1670959] Re: systemd-resolved using 100% CPU

Andreas Hasenack andreas at canonical.com
Fri Jul 27 14:25:04 UTC 2018


And looks like we need to find out what is adding 127.0.0.1 to
resolv.conf. It could come from many different sources, like a
nameserver configuration in some /etc/network/interfaces carried over
from xenial, or something in network-manager, etc. I guess you could
start with a brute-force grep -r on /etc for 127.0.0.1?

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1670959

Title:
  systemd-resolved using 100% CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions



More information about the Ubuntu-server-bugs mailing list