Today I had upgraded to Mageia 9 and on system boot it said "failed to start network.service". I had to start and enable NetworkManager by hand to get the networking up: > systemctl start NetworkManager > systemctl enable NetworkManager Likely > rpm -e network-scripts would be sufficient to get rid of the failed-to-start boot message. However I haven’t done that yet to leave some space for testing on how to switch networking automatically on an upgrade. Upgrade procedure was invoked like this from multi-user target: > urpmi.removemedia -a > urpmi.addmedia --distrib --mirrorlist http://mirrors.mageia.org/api/mageia.9.i586.list > urpmi --replacefiles --auto-update --auto --download-all
Created attachment 13583 [details] journalctl -b (output)
I don’t know whether it has anything to do with the switch of the systemd-networking scripts but evolution says it is forced offline: $ evolution evolution-shell-Message: 01:26:07.025: Network disconnected. Forced offline. works with Thunderbird.
Thank you for the report. Did you have NetworkManager enabled before the upgrade? If so, could this bug be "NW enabled does not survive upgrade"? What look like the relevant lines from the journal (thanks for attaching that) before you started NM manually: Dec 19 00:40:03 localhost systemd-sysv-generator[516]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Dec 19 00:40:03 localhost systemd-sysv-generator[516]: SysV service '/etc/rc.d/init.d/network-auth' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Dec 19 00:40:03 localhost systemd-sysv-generator[516]: SysV service '/etc/rc.d/init.d/network-up' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. ... Dec 19 00:40:14 localhost systemd[1]: Starting network-up.service.. ... Dec 19 00:40:17 localhost systemd[1]: Starting network.service.. Dec 19 00:40:17 localhost network[918]: WARN : [network] You are using 'network' service provided by 'network-scripts', which are now deprecated. Dec 19 00:40:17 localhost network[939]: You are using 'network' service provided by 'network-scripts', which are now deprecated. Dec 19 00:40:17 localhost systemd[1]: Started ModemManager.service. Dec 19 00:40:17 localhost network[918]: WARN : [network] 'network-scripts' will be removed from distribution in near future. Dec 19 00:40:17 localhost network[940]: 'network-scripts' will be removed from distribution in near future. Dec 19 00:40:18 localhost network[918]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network management. Dec 19 00:40:18 localhost network[943]: It is advised to switch to 'NetworkManager' instead for network management.
CC: (none) => lewyssmith
To my knowledge I was using NetworkManager, but the service was likely not started directly via systemd but via the network-scripts package which is now deprecated.
Thanks. You would know if you were using NM: you have to do specific things to do so.
Assignee: bugsquad => basesystemSummary: Mageia 9 Upgrade procedure: automatically switch to NetworkManager => After Mageia 9 Upgrade: "failed to start network.service", needed to start NetworkManager by handCC: lewyssmith => (none)
To my knowledge NetworkManager runs by default on any Mageia 8 or previous, even if you have not configured that manually. Here on the System76 Darp5 x86_64 I run Mageia 8 and as you can see like follows NetworkManager is active: > nmcli conn show --active NAME UUID TYPE DEVICE enp57s0f1 7c783845-a876-43a6-9a7b-1ea148e8a6ac ethernet enp57s0f1 timecapsule 90686813-9666-43a6-8811-1d4b9d8899f5 wifi wlp58s0 If NetworkManager is running a world globe with plugged cable is shown in the system tray; that is where you can select a Wifi or some ethered connection. What I suppose that Mageia 9 does/ wants to do now is to drop the traditional nm-applet and network-scripts which could connect without NetworkManager and replace all of that by nowadays established default solution which is NM-only.
(In reply to Elmar Stellnberger from comment #6) > To my knowledge NetworkManager runs by default on any Mageia 8 or previous, Wrong. Mageia uses it's own tool called net-applet. Only GNOME (wehen installed from the Live-Media uses networkmanager by default. All other cases must switch to networkmanger manually). (In reply to Elmar Stellnberger from comment #6) > If NetworkManager is running a world globe with plugged cable is shown in > the system tray; No. This depends on the used DE but for most DE's, the globe is a sign that Mageias own tool net-applet is in use. The icon for networkmanager is ether a Wifi symbol (for wifi) or a hardwired computer symbol (LAN) (In reply to Elmar Stellnberger from comment #6) > drop the traditional nm-applet There is nothing like nm-applet. The Mageia standard tool is called net_applet which comes from the package draks-net-applet. https://wiki.mageia.org/en/Switching_to_networkmanager
(In reply to sturmvogel from comment #7) > net_applet which comes from the package draks-net-applet. Its drakx-net-applet
(In reply to Elmar Stellnberger from comment #0) > Today I had upgraded to Mageia 9 and on system boot it said "failed to start > network.service". This sounds like that you didn't follow the instructions how to switch to networkmanager on your MGA8 box prior upgrading to MGA9 Alpha. According our instructions you need to disable the legacy network startup services by running: # systemctl mask network.service; systemctl mask network-up https://wiki.mageia.org/en/Switching_to_networkmanager
Pardon nm-applet is of course the NetworkManager applet. The drakx-net-applet is called net_applet: > rpm -qf $(which net_applet) drakx-net-applet-2.55-1.mga8 > rpm -qf $(which nm-applet) networkmanager-applet-1.16.0-1.mga8
sturmvogel: It should be done automatically when you upgrade to network-scripts.mg9 (currently 10.04-2) by an rpm post-install scriptlet. Besides this you need to enable NetworkManager explicitly because it isn´t started otherwise; those who don´t know about nm will stay offline otherwise. Futhermore if one does not need network-scripts.mg9 at all there needs to be an obsoletes network-scripts tag in the new networkmanager.mg9 package.
I plan to upgrade also my Celsius Core 2 notebook to Mageia 9. There I could see if NetworkManager stays enabled on upgrade (here with Mageia 8 in deed it says: NetworkManager.service; enabled; vendor preset: enabled). This is an old Mg8-times Cauldron, though. At me disabling rather than masking appears to have been sufficient for network.service and network-up.
(In reply to Elmar Stellnberger from comment #12) > At me disabling rather than masking > appears to have been sufficient for network.service and network-up. There is a difference between disabling and masking a service. There is plenty information about this available. So by not following the guide you create your problems yourself.
AFAIK masking is more far-reaching than disabling but here I have carefully tested that disabling would be sufficient. Besides this as said in Comment #11 it should be done automatically. Please DO also read and refer to what I write here!! Let me know when I should start the upgrade process for the Celsius. Currently I don´t need that computer productively so I can wait with it until things shall be fixed here. How can it be that here on my Darp5 it says "NetworkManager.service; enabled; vendor preset: enabled" if NM isn´t already supposed to be the default for Mg8?
(In reply to Elmar Stellnberger from comment #14) > How can it be that here on my Darp5 it says "NetworkManager.service; > enabled; vendor preset: enabled" if NM isn´t already supposed to be the > default for Mg8? You didn't tell which DE you are using and from which media you installed this box. net-applet is the standard tool for Mageia since Mandrake times. Networkmanager is not. Except for GNOME installed from Live Media (starting from Mageia 7). So you either tinkered your box (and can't remember) or you installed from Gnome Live. Period. And btw the package description of "network-scripts" is straight forward: "This package contains the legacy scripts for activating & deactivating of most network interfaces. It also provides a legacy version of 'network' service. The 'network' service is enabled by default after installation of this package, and if the network-scripts are installed alongside NetworkManager, then the ifup/ifdown commands from network-scripts take precedence over the ones provided by NetworkManager. If user has both network-scripts & NetworkManager installed, and wishes to use ifup/ifdown from NetworkManager primarily, then they has to run command: $ update-alternatives --config ifup Please note that running the command above will also disable the 'network' service."
Also from Bug 30859 and Bug 30857 I know that I was (and am) using NetworkManager by default under Mageia 8 on the x64 Darp5 machine. I had only additionally started net_applet a few times for testing purposes. Could it be that this comes from the Xfce desktop environment? Basically why does it say "vendor preset: enabled"?
According bug 25340 there is only a request to use Networkmanager under Xfce as standard.
* Bug 31299 may be related. * This bug was tested with LXDE and the x32 Gericom SilverSeraph.