There is some configuration that leads to a loop between these two
resolvers, and that is what causes the cpu usage. If we could get a step
by step way to reproduce it, it could probably be addressed.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscr
I don't know what is the use case you guys have that you have to have
dnsmasq and resolvconf installed. Maybe there is none and this is just
an artifact from a release upgrade.
In Bionic, I only have dnsmasq-base (not dnsmasq) installed, and no
resolvconf.
Looking at the initscript from dnsmasq,
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 o
What do you guys have inside /etc/resolvconf? In terms of directories,
files, and their contents.
Do you have the resolvconf package installed by any chance?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launc
@diepes, interesting. Looks like there was a loop going on there.
Can everybody please check their /etc/resolv.conf to see if something
similar might be happening with it?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
http
