on Ubuntu 16.10, for some minute after wifi connection, systemd-journal
, systemd-resolve
and dnsmasq
tend to use almost 150% of CPU.
Is this normal?
on Ubuntu 16.10, for some minute after wifi connection, systemd-journal
, systemd-resolve
and dnsmasq
tend to use almost 150% of CPU.
Is this normal?
Suggested by another Steps of solution
Add the line
DNSMASQ_EXCEPT=lo
to/etc/default/dnsmasq
Restart dnsmasq via
Say Thanks If I helped, It went back to normal and does NOT screw around with other apps, as the previous method DID.
Cheers, Mark
I had the same Problem in 18.04.
systemd-resolved
anddnsmasq
tend to loop. I solved it this way:Add or uncomment the following line in
/etc/default/dnsmasq
:Create your own
resolv
file (/etc/resolv.personal
) to define nameservers. You can use any nameserver here. I took two from OpenNIC.In
/etc/dnsmasq.conf
add or uncomment the following line:Then restart
dnsmasq
and disable the default resolver:systemd-resolved
.Read
man systemd-journald
; Readman systemd-resolve
; Readman dnsmasq
; Readman journalctl
.Check your log files in
/var/log/*
.From the little you've said, it looks like a whole bunch of log entries are being made (Investigate why!), and some part of your logging system is trying to resolve "
domain names, IPv4 and IPv6 addresses, DNS resource records or services with the systemd-resolved.service(8) resolver service.
". (Readman 8 systemd-resolved.service
.) This "name resolution" is what's taking the time.Normal? When Linux runs on everything from Systems-On-Chip to members of the Top 50 Supercomputers, what does "Normal" mean?