Bugzilla – Bug 741588
network sometimes comes not up
Last modified: 2012-02-06 15:19:47 UTC
Summary basically says it all: During holidays I updated two of my home machines to 12.1, but now sometimes the network simply does not come up after boot. All I find in /var/log/messages is this: Jan 16 06:31:46 Pangaea dbus[743]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. If I type "rcnetwork restart" as root, I only get the useless information "redirecting to systemd" and the net still will not work. The message "no such file or directory" is useless as well, since it does not tell me WHICH file or directory is missing. If I type the reload command, I get: Pangaea:~ # systemctl status dbus-org.freedesktop.NetworkManager.service dbus-org.freedesktop.NetworkManager.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) Pangaea:~ # I should note that I get exact the same output when the network startup at boot was successful! So this output is useless as well. I assume the problems are introduced by systemd, which may be a nice toy project, but if it is unable to successfully complete such basic tasks as setting up the network reliably, we are several steps further to Windows.
Hubert, The log doesn't affect the network, the NetworkManager use below service file, you can got some result like below. # systemctl status NetworkManager.service
Federic, Also from my /var/log/messages I found the log like below. [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. So what's the dbus-org.freedesktop.NetworkManager.service used for? Thanks!
dbus-org.freedesktop.NetworkManager.service is used by dbus when systemd is running, for automatic service activation ie if NM isn't running, systemd would start it on behalf of dbus. This is disabled on purpose because NM should only be started by initscript / systemd .service and not "on demand" (it would conflict with ifup network service).
I "solved" this problem by dropping systemd and using sysvinit instead. In contrast to systemd, sysvinit is capable of booting the system correctly and reliably and not only with a probability of 70 to 80%. *** This bug has been marked as a duplicate of bug 737636 ***