- Package:
- network-manager
- Source:
- network-manager
- Description:
- network management framework (daemon and userspace tools)
- Submitter:
- Josh Triplett
- Date:
- 2026-04-28 00:31:03 UTC
- 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'.
retitle 799603 Should not monitor or open /run/network/ifstate if ifupdown plugin disabled thanks Later in the same log, NetworkManager also tries to open that file: Sep 20 12:34:12 x NetworkManager[20704]: <warn> Error: failed to open /run/network/ifstate
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.)
I downgraded the log message from warn to info. That said, I'd be happy to take a patch which disables the ifstate monitoring completely, if the ifupdown plugin has been disabled. Regards, Michael
found 799603 1.52.1-1 quit Similar stuff in my log: Apr 28 00:15:58 MyHost NetworkManager[970]: <info> [1777328158.2966] monitoring ifupdown state file '/run/network/ifstate'. … Apr 28 00:15:59 MyHost NetworkManager[970]: <info> [1777328159.0159] failed to open /run/network/ifstate ifupdown was uninstalled recently, and there is no /run/network.