[Expired for dnsmasq (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/167095
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100%
Same issue on Ubuntu 18.4, that occurred after system startup.
Linux ali-GE620DX 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hi Jasem,
it seems you are hitting a similar but not the necessarily same issue.
As outlined before all discussions here ended as incomplete unable to be
actioned and needs clear steps to reproduce to continue.
I'd ask you to file a new bug for your case and there provide as much
info as possible
I'm affected by this bug, but using dnsmasq-base employed by
NetworkManager and not dnsmasq package. The dnsmasq is what is consuming
one core of the CPU 100% after a few minutes, not systemd-resolved.
After heating the CPU for a few minutes, it drops again and the cycle
repeats after a while. I ke
For other souls facing this "Medium" issue,
a hammer-ish workaround that works for me:
1) Run:
apt-get install cpulimit
2) edit /lib/systemd/system/systemd-resolved.service:
2a) Comment out:
#Type=notify
2b) Replace line (may want to remove the -k to let cpulimit throttle it):
#ExecStart=!!/li
>From the above comments I think it's clear that the problem is caused by
some kind of misconfiguration resulting in a loop. It isn't clear if
that misconfiguration is coming from a user error or from some bug in an
upgrade path somewhere. If the latter, then it's a valid bug. However,
since we don
Also happening to me after 16.04 -> 18.04 LTS upgrade (via do-release-
upgrade)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications
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
Bugs, which is subscrib
This annoying bug affected all upgrades to Bionic and Cosmic Cuttlefish
I did so far and also effects Cosmic Cuttlefish. systemd-resolv and
dnsmasq consume each 100% CPU and internet access becomes extremely
slow.
My latest workaround is to disable automatic overwriting to
/etc/resolf.conf with su
I have this on Ubuntu 18.04. In my case I use dnsmasq with a custom
configuration providing DHCP and DNS to multiple bridges (Virtual
Machines and containers). So I need them both (in so far as I need
dnsmasq and am being forced to use systemd).
The problem is a DNS loop between systemd and dnsmas
I also had this issue after upgrading to 18.04. During the upgrade, I
got asked if I wanted to keep or replace my /etc/dnsmasq.conf, I opted
to replace with the package maintainer's version. The old config file
had the option interface=enp0s25, the new one does not. I don't
know/remember where this
I also think it's an upgrade artifact. It happened on my upgraded laptop but
not in the freshly installed desktop machine.
The problem in the laptop now (I think) hostapd that requires dnsmasq.
The workaround cited by @ahasenack in #49 seems to work.
--
You received this bug notification becau
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,
It seems to be dnsmasq itself:
/etc/init.d/dnsmasq:163:echo "nameserver 127.0.0.1" |
/sbin/resolvconf -a lo.$NAME
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
system
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
This solution works, but it's not persistent. /etc/resolv.conf is a symlink to
/run/resolvconf/resolv.conf, which is ephemeral. It'll be recreated as
127.0.0.1.
Any news on an actual fix for this, rather than just a workaround?
Thanks!
--
You received this bug notification because you are a mem
I just started noticing this issue on my machine today. Ubuntu 18.04. I
also had nameserver 127.0.0.1 in /etc/resolv.conf. Changed to
127.0.0.53, per diepes' comment and CPU calmed down for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
This happened on my machine, and diepes's fix worked for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about this
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Ubuntu 18.04.
edited $sudo vim /etc/resolv.conf
changed
nameserver 127.0.0.1
to
nameserver 127.0.0.53
CPU calmed down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-re
I also trying confront with this problem, but there is no solution at all. I
tried to disable the systemd-resolved service but after that my domain resolver
stop working and I lost access to webpages. I also have dnsmasq. I don't know
why but I think this service is come from Ubuntu 16.04.
I upg
Just to chime in: Noticed slow machine and systemd-resolved taking 100%
cpu. Edited /etc/systemd/resolved.conf to DNSSEC=no (not off, as "no"
was commented out in the file). Tried systemctl restart systemd-
resolved, but nothing changed. Tried killall systemd-resolved, nothing.
Tried killall -9
same issue with 17.10, takes a complete core,
DNSMASQ_EXCEPT=lo is not working, also after reboot, it still takes a core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved
Adding
DNSMASQ_EXCEPT=lo
to
/etc/default/dnsmasq
solves the problem in my case, kubuntu 17.10, kernel 4.15.rc7,
for several days now.
Peter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/+s
Christian: I've tried as I believe you have asked.
When in the bad case (I comment out the line: DNSMASQ_EXCEPT=lo and then
reboot):
- Running this did not resolve the issue: `sudo resolvconf -a lo.dnsmasq`
- Running this did not resolve the issue: `echo "nameserver 127.0.0.1" |
/sbin/resolvco
Maybe interesting things to note:
1. When in bad state:
- The mentioned ENV var change in /etc/default/dnsmasq and `sudo systemctl
restart dnsmasq` immediately resolves the issue
2. When in good state:
- Commenting out the ENV var and running `sudo systemctl restart dnsmasq`
does not immedia
Interesting James,
so there is a little twist that might be related and lead to a resolution.
Usually the service of dnsmasq would add itself to the resolvconf server set.
It does so in:
start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be
Also seeing this issue in Ubuntu 17.10 (artful) with:
dnsmasq-base 2.78-1
systemd 234-2ubuntu12.1
I can confirm that following https://askubuntu.com/a/968309/ resolves
the issue!
Steps to fix the issue:
Added this line to /etc/default/dnsmasq:
DNSMASQ_EXCEPT=lo
Then restarting dns
Is there an official solution yet? BTW https://askubuntu.com/a/968309/
seemed to help me out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage
@ Michael Roth (mdroth)
On zesty and later /etc/resolv.conf must not list "nameserver 127.0.0.1" this
seems to be broken configuration state.
I am concerned how you got into such a state. Is your network managed by
ifupdown with /etc/network/interfaces or NetworkManager? do you have resolvconf
hi All,
Is it possible to eliminate systemd-resolved from the system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about th
Hi Michael,
I'm certainly the least expert in this case - I was just trying to help mapping
that other case I have seen.
Your ouput tells (me oO) that your resolvd talks to:
1. a link scope DNS 192.168.2.254 on wlp4s0
2. is set up to talk to a gloabl dns at 127.0.0.1
IIRC it will ask both and wh
@ChristianEhrhardt: I'm not sure how to determine whether systemd-
resolver is forwarding back to dnsmasq, hopefully it's clear from the
output:
mdroth@sif:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND --
"if dnsmasq's option "--dns-loop-detect" via DNSMASQ_OPTS in
/etc/default/dnsmasq."
this does not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Hmm I knew I remembered something related ...
In bug 1694156 we have had a - what appears to me as - similar case.
There we could track it down to a config issue, but maybe you here are affected
by the same issue yet without a simple config issue to fix.
The clue there was, that that dnsmasq was
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/
Have the same issue with 17.04. Especially then qBittorent starting.
Also huge lag with apt update resolve servers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved usin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
sy
It seems that the problem is that dnsmasq is forwarding DNS queries to
the systemd-resolved stub server, but they are incompatible in some
way:. From /var/log/syslog:
Jun 12 17:05:34 sparkly dnsmasq[1177]: using nameserver 127.0.0.53#53
Jun 12 17:05:49 sparkly dnsmasq[1177]: Maximum number of con
I just tried the workaround Kai-Heng mentioned in #9 above: I added
'DNSSEC=off' to /etc/systemd/resolved.conf, then rebooted.
Unfortunately I'm still seeing this CPU problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I've also run into this CPU problem on 17.04. Like tlk, I had to
install dnsmasq because I'm running a hotspot on a USB wifi device, and
the system log indicated that it wouldn't work unless dnsmasq is
installed.
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
--
Y
On another not, it seems that dnsmasq was dropped intentionally in
regards to NM (https://launchpad.net/ubuntu/zesty/+source/network-
manager/+changelog), in favor of systemd-resolved. But when I tried to
NAT my desktop's connection to a laptop initially it didn't work out, so
I looked into journal
On a fresh 17.04 install systemd-resolved didn't give me any grief until I've
manually installed dnsmasq, because I wanted NetworkManager to share my
connection from desktop to a laptop and without dnsmasq it fails to do so.
Now I'm hitting this CPU hog problem.
--
You received this bug notific
I see it all the time after an upgrade to 17.04. Medium priority seems
an euphemism. This is a true showstopper. It is not just systemd-
resolved taking a whole core. Dnsmasq takes half of another. The cpu
runs hot. In a laptop, batteries drain in a snap.
Has this to do with https://unix.stackexch
Actually it's happening continuously, it does not even require a wakup,
of wifi reconnection or anything...
It's a complete useless peace of crap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/167095
Recently I can definitely reproduce the issue anytime.
It's extremely annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications
> This is a good workaround, but perhaps the actual fix should be to
remove the package on upgrade to 17.04?
What do you mean by this?
The fix should not ever something like this.
There is reason why dnsmasq is installed on these machines.
This is a workaround by not good.
--
You received this
Weird, I can reproduce the issue again after about 1-2 weeks of silence...
I can test the DNSSEC=off setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100%
@clvx: I think the other bug is unrelated, although maybe that's what
you're running into instead of this one.
I was also able to fix this problem by removing dnsmasq:
* sudo apt remove dnsmasq
As soon as I did that, both processes dropped to nothing, and DNS still
resolves.
This is a good work
I cannot reproduce the issue very recently, for about ~1 week.
Let me check it in another location tomorrow.
ii dnsmasq
2.76-5all
Small caching DNS proxy
Kai-Heng, At least for me, it's working now. Btw, before changing
DNSSEC=off, I tested removing dnsmasq to keep only systemd-resolved(as
someone mentioned above), and systemd-resolved didn't resolve any
domain. I had to install dnsmasq again to have some sort of connection.
Is this bug related to
Does put 'DNSSEC=off' to /etc/systemd/resolved.conf help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about this bug go to:
** Description changed:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like starting
the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(3
1. top
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
19147 systemd+ 20 0 50848 6232 4572 R 99.0 0.1 5:43.81
systemd-resolve
1472 dnsmasq 20 0 57020 3084 2620 R 63.1 0.0 44:0
This bug still exists in ubuntu 17.04 release version!
100% CPU with "Unassigned", OMG!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notif
lxc and lxd do not depend on dnsmasq in Ubuntu 17.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about this bug go to:
http
Remove dnsmasq is not an option when you are using lxd/lxc.
You may reassign this bug to dnsmasq.
A temporary solution can be to append your nameserver in
/etc/resolvconf/resolv.conf.d/head
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Also had 100% CPU after upgrade, together with failing DNS resolution and
dnsmasq complaining about having reached the max number of simultaneous
requests.
Removing dnsmasq has fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It also happens when you are connected by wire. XPS13 9350 affected
after upgrading from 16.10(yaketti) to 17.04(zetsy(.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about this bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
sy
64 matches
Mail list logo
