journald forwards to syslog with facility=KERN on everything
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Debian) |
Confirmed
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Committed
|
Low
|
Unassigned |
Bug Description
NetworkManager's copious syslog output is for some reason making its way into my /var/log/kern.log file. This includes a couple dozen <info> lines at startup and a similar amount when connecting to WiFi with DHCP.
The NM man page states that the default facility should be DAEMON, as does the NM wiki -- see http://
Hopefully, it goes without saying that the KERN facility is reserved for the kernel and shouldn't be messed with by anything from userland.
Nothing in the rsyslog configs references kern.log except the one expected line:
/etc/rsyslog.
Nothing in NetworkManager.conf references syslog or its facilities. Oh, and these messages do also correctly make it to syslog.log. I've no idea how or why they also end up in kern.log, though.
This doesn't happen on Ubuntu 14.04:
% zgrep -cv kernel: /var/log/kern.log*
/var/log/kern.log:0
/var/log/
/var/log/
/var/log/
/var/log/
On Ubuntu 16.04.1, NM is the major culprit, although there were also a few lines from gnome-session:
% zgrep -cv kernel: /mnt/var/
/mnt/var/
/mnt/var/
% zgrep -v kernel: /mnt/var/
17
% zgrep -v kernel: /mnt/var/
0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 16 06:53:42 2016
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-08-13 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.5 metric 600
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlp3s0 wifi connected /org/freedeskto
enp0s25 ethernet unavailable /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.0 connected started full enabled enabled enabled enabled enabled
Changed in network-manager (Ubuntu): | |
assignee: | nobody → Aron Xu (happyaron) |
Changed in gnome-session (Ubuntu): | |
importance: | Undecided → Low |
Changed in network-manager (Ubuntu): | |
importance: | Undecided → Low |
summary: |
- NM and gnome-session seem to be syslogging with facility KERN + journald forwards to syslog with facility=KERN on everything |
affects: | gnome-session (Ubuntu) → systemd (Ubuntu) |
Changed in systemd: | |
status: | Unknown → New |
Changed in systemd (Debian): | |
status: | Unknown → Confirmed |
Changed in network-manager (Ubuntu): | |
status: | Confirmed → Incomplete |
no longer affects: | network-manager (Ubuntu) |
Changed in systemd: | |
status: | New → Fix Released |
This is actually getting worse in Debian stretch, and there affects almost 2 dozen packages, so it might not even be the packages' (NetworkManager, gnome-session) fault. Anyway, https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 858399