Description of problem: I have been seeing for some time that the network-up service takes too long to start, delaying the startup of Mageia by more than 10 seconds in most cases. I have observed this behavior on several computers with a clean installation of the system, so it may be some problem in systemd itself in the hierarchy of how this service starts during system startup. Version-Release number of selected component (if applicable): Network-up.service How reproducible: Boot the system and run as root in terminal: systemd-analyze blame Steps to Reproduce: 1. Boot the sistem. 2. Run terminal as root 3. Run "systemd-analyze blame" for see the time init of network-up.service
Created attachment 14521 [details] Terminal output showing network-up.service startup time Terminal output showing network-up.service startup time
That not look too much for me systemd-analyze blame 32.406s fail2ban.service 27.998s httpd.service 27.486s php-fpm.service 27.250s libvirtd.service 13.329s sshd.service 12.974s network-up.service 11.683s shorewall.service 7.071s systemd-udev-settle.service 5.870s dev-sda1.device 4.958s udisks2.service 4.482s network.service 4.009s systemd-tmpfiles-setup-dev.service 3.746s systemd-journal-flush.service 3.322s upower.service 3.025s avahi-daemon.service 2.969s dbus.service 2.906s rtkit-daemon.service 2.882s systemd-machined.service 2.658s dkms-autorebuild.service 2.317s mandriva-everytime.service 2.199s sensord.service 2.105s chronyd.service 1.705s mga-bg-res.service 1.096s mdmonitor.service 1.057s polkit.service 938ms preload.service 935ms lvm2-monitor.service 907ms noip.service 800ms systemd-vconsole-setup.service 661ms systemd-logind.service 638ms user@1000.service 623ms mdmonitor-takeover.service 622ms modprobe@configfs.service 620ms modprobe@drm.service 618ms modprobe@fuse.service 615ms systemd-fsck-root.service 609ms systemd-journald.service 602ms msec.service 538ms systemd-sysctl.service 536ms shorewall6.service 510ms systemd-udevd.service 478ms systemd-binfmt.service 439ms systemd-random-seed.service 405ms numlock.service 383ms dev-hugepages.mount 382ms dev-mqueue.mount 382ms sys-kernel-debug.mount 381ms sys-kernel-tracing.mount 380ms kmod-static-nodes.service 295ms plymouth-quit-wait.service 292ms plymouth-quit.service 291ms lm_sensors.service 254ms systemd-modules-load.service 252ms systemd-udev-trigger.service 249ms systemd-fsck@dev-disk-by\x2duuid-9f2e3e7b\x2d9302\x2d4fb1\x2d9297\x2d2faef39a6b6b.service 243ms dmraid-activation.service 233ms gpm.service 199ms systemd-tmpfiles-setup.service 153ms acpid.service 139ms systemd-user-sessions.service 138ms proc-sys-fs-binfmt_misc.mount 115ms plymouth-start.service 102ms dev-disk-by\x2duuid-ac50cb2a\x2d7731\x2d479b\x2d94f1\x2de90cc4f90106.swap 98ms dracut-shutdown.service 80ms systemd-remount-fs.service 79ms power-profiles-daemon.service 77ms systemd-update-utmp.service 44ms plymouth-read-write.service 39ms home.mount 10ms user-runtime-dir@1000.service 9ms systemd-update-utmp-runlevel.service 8ms sys-fs-fuse-connections.mount 8ms sys-kernel-config.mount 3ms modprobe@dm_mod.service 3ms modprobe@loop.service 3ms tmp.mount
Long startup times for network-up can be caused by it trying to start for network interfaces that are no longer present. Check for any files other then ifcfg-lo shown by $ ls -l /etc/sysconfig/network-scripts/ifcfg* If any are for devices not being used, either delete them (if the device does not exist) or disable them (if the nic exists but is not being used) by change ONBOOT=yes to ONBOOT=no
CC: (none) => davidwhodgins
I can't disable any network interfaces, because I use them. And I only have the Wi-Fi networks that I usually use. If this is the only solution, we can consider the bug "unsolved" and close it. Greetings!
Jose, can you look at Bug 33140, which is in the same area. I see DaveH is already CC'd here as well as there.
CC: (none) => lewyssmith
Yes, I have tried as indicated in the other bug to switch to networkmanager on my computer. It certainly works better than net_applet and I find it more intuitive for any user. Just in the wiki instructions it recommends to disable network-up.service, and now everything seems to work as it should. I take this opportunity to comment that following the wiki instructions on a laptop, I noticed that the first commands disable the wlan, making it impossible to follow the tutorial and install plasma-applet or networkmanager. It should be changed and first install the packages and then run the commands (I did and it works fine). Thanks for the information on bug 33140.
https://wiki.mageia.org/en/Switching_to_networkmanager updated
Thanks to all contibutors; and Dave for updating the NM wiki. I agree with comment 2 "not look too much for me": 10-11s. Slow (I have 3-6s), but not silly. Given that Jose seems happier with Network Manager, I think we can close this.
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED