Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#799603: Should not monitor /run/network/ifstate if ifupdown plugin disabled
83 views
Skip to first unread message
Josh Triplett
Sep 20, 2015, 3:40:03 PM9/20/15
to
Package: network-manager
Version: 1.0.6-1
Severity: normal
I have the ifupdown plugin disabled in
/etc/NetworkManager/NetworkManager.conf; however, I still see the
following in syslog:
Sep 20 12:34:12 x NetworkManager[20704]: <info> monitoring ifupdown state file '/run/network/ifstate'.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.113+nmu3
ii dbus 1.10.0-3
ii init-system-helpers 1.23
ii isc-dhcp-client 4.3.3-3
ii libbluetooth3 5.33-1
ii libc6 2.19-20
ii libdbus-1-3 1.10.0-3
ii libdbus-glib-1-2 0.102-1
ii libglib2.0-0 2.44.1-1.1
ii libgnutls-deb0-28 3.3.17-1
ii libgudev-1.0-0 230-2
ii libmm-glib0 1.4.10-1
ii libndp0 1.4-2
ii libnewt0.52 0.52.18-1
ii libnl-3-200 3.2.26-1
ii libnl-genl-3-200 3.2.26-1
ii libnl-route-3-200 3.2.26-1
ii libnm0 1.0.6-1
ii libpam-systemd 226-3
ii libpolkit-agent-1-0 0.105-12
ii libpolkit-gobject-1-0 0.105-12
ii libreadline6 6.3-8+b3
ii libsoup2.4-1 2.50.0-2
ii libsystemd0 226-3
ii libteamdctl0 1.18-1
ii libuuid1 2.27-3
ii lsb-base 9.20150917
ii policykit-1 0.105-12
ii udev 226-3
ii wpasupplicant 2.3-2.1
Versions of packages network-manager recommends:
pn crda <none>
ii dnsmasq-base 2.75-1
ii iptables 1.4.21-2+b1
pn iputils-arping <none>
pn modemmanager <none>
pn ppp <none>
Versions of packages network-manager suggests:
pn avahi-autoipd <none>
pn libteam-utils <none>
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=keyfile
dhcp=internal
[ifupdown]
managed=false
-- no debconf information
Version: 1.0.6-1
Severity: normal
I have the ifupdown plugin disabled in
/etc/NetworkManager/NetworkManager.conf; however, I still see the
following in syslog:
Sep 20 12:34:12 x NetworkManager[20704]: <info> monitoring ifupdown state file '/run/network/ifstate'.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.113+nmu3
ii dbus 1.10.0-3
ii init-system-helpers 1.23
ii isc-dhcp-client 4.3.3-3
ii libbluetooth3 5.33-1
ii libc6 2.19-20
ii libdbus-1-3 1.10.0-3
ii libdbus-glib-1-2 0.102-1
ii libglib2.0-0 2.44.1-1.1
ii libgnutls-deb0-28 3.3.17-1
ii libgudev-1.0-0 230-2
ii libmm-glib0 1.4.10-1
ii libndp0 1.4-2
ii libnewt0.52 0.52.18-1
ii libnl-3-200 3.2.26-1
ii libnl-genl-3-200 3.2.26-1
ii libnl-route-3-200 3.2.26-1
ii libnm0 1.0.6-1
ii libpam-systemd 226-3
ii libpolkit-agent-1-0 0.105-12
ii libpolkit-gobject-1-0 0.105-12
ii libreadline6 6.3-8+b3
ii libsoup2.4-1 2.50.0-2
ii libsystemd0 226-3
ii libteamdctl0 1.18-1
ii libuuid1 2.27-3
ii lsb-base 9.20150917
ii policykit-1 0.105-12
ii udev 226-3
ii wpasupplicant 2.3-2.1
Versions of packages network-manager recommends:
pn crda <none>
ii dnsmasq-base 2.75-1
ii iptables 1.4.21-2+b1
pn iputils-arping <none>
pn modemmanager <none>
pn ppp <none>
Versions of packages network-manager suggests:
pn avahi-autoipd <none>
pn libteam-utils <none>
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=keyfile
dhcp=internal
[ifupdown]
managed=false
-- no debconf information
Al Ma
Apr 15, 2023, 7:20:04 PM4/15/23
to
found 799603 1.30.6-1+deb11u1
quit
Affects me. In the journal log I see “NetworkManager[885]: <warn> [1681591017.6980] Error: failed to open /run/network/ifstate”. As this is not only a warning but also an error, who has done what wrong? (I have 184 occurrences of “error” in the output of `journalctl -b`; I'd really wish to know which one is no more than a printf resulting from sloppy, careless programming and which one also leads to the end-user problems at hand, whichever they may be.)
0 new messages