systemd-resolved spams the system log with useless “Processing query...” messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If you are running ‘journalctl -f’ to try to debug some other problem, you are constantly interrupted by zillions of these messages from systemd-resolved:
Mar 26 00:53:27 change-mode systemd-
Mar 26 00:53:27 change-mode systemd-
Mar 26 00:53:30 change-mode systemd-
Mar 26 00:53:30 change-mode systemd-
Mar 26 00:53:30 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
Mar 26 00:53:31 change-mode systemd-
This was fixed upstream in v233 by downgrading this message from log_info to log_debug:
https:/
Changed in systemd: | |
status: | Unknown → Fix Released |
Dont get your spam: services. mozilla. com”: Name or service not known
oem@u64:~$ journalctl | grep query
Mar 26 07:15:44 u64 geoclue[2802]: Failed to query location: Error resolving “location.
and seems already been fixed:
systemd (232-21) unstable; urgency=medium
* resolved: Downgrade "processing query..." message to debug.
It doesn't really add much value in normal operation and just spams the
log. (Closes: #858197)
-- Michael Biebl <email address hidden> Tue, 21 Mar 2017 19:52:17 +0100