Ci risiamo: Failed to start Network Manager Wait Online

Da un po’, durante il boot, ottengo di nuovo il messaggio “Failed to start Network Manager Wait Online” (vedi http://forum.fedoraonline.it/viewtopic.php?pid=233204), con l’effetto di ritardare l’accesso al desktop di 20-30 secondi.

Qualche output:

  1. systemd-analyze (il boot avviene da ssd):

$ systemd-analyze Startup finished in 3.309s (kernel) + 3.447s (initrd) + 55.311s (userspace) = 1min 2.068s
2) systemd-analyze blame:

$ systemd-analyze blame 30.117s NetworkManager-wait-online.service 21.313s plymouth-quit-wait.service 6.505s uptrack-prefetch.service 2.879s plymouth-start.service 2.839s abrtd.service 1.800s mariadb.service 1.603s systemd-udev-settle.service 1.037s boinc-client.service 903ms firewalld.service 730ms cups.service 724ms systemd-journal-flush.service 716ms uptrack.service 598ms [email protected] 590ms dev-sdc1.device 456ms mnt-Windows-XP64.mount 454ms libvirtd.service 426ms lvm2-monitor.service 362ms smb.service 330ms ddclient.service 329ms mnt-Windows-Dati.mount 326ms systemd-logind.service 320ms accounts-daemon.service 288ms systemd-fsck@dev-disk-by\x2duuid-b75c4fe9\x2da2e5\x2d478b\x2d9425\x2dcf5b18ad8f39.service 237ms console-kit-log-system-start.service 219ms iio-sensor-proxy.service 213ms home.mount 205ms packagekit.service 191ms rtkit-daemon.service 186ms avahi-daemon.service 166ms udisks2.service 165ms systemd-fsck@dev-disk-by\x2duuid-438d24f3\x2d06e2\x2d4fa4\x2dbc4c\x2d3933655f9845.service 159ms mcelog.service 158ms chronyd.service 152ms systemd-modules-load.service 150ms netcf-transaction.service 146ms lm_sensors.service 145ms restorecond.service 144ms livesys.service 142ms gpm.service 139ms colord.service 134ms proc-fs-nfsd.mount 130ms systemd-udev-trigger.service 116ms gssproxy.service 115ms gdm.service 114ms rsyslog.service 110ms systemd-fsck@dev-disk-by\x2duuid-3ad6e5a2\x2ded64\x2d44a0\x2d842b\x2dbcdb8aafe603.service 107ms systemd-binfmt.service 104ms systemd-vconsole-setup.service 97ms systemd-tmpfiles-setup.service 96ms polkit.service 93ms dmraid-activation.service 89ms systemd-tmpfiles-setup-dev.service 85ms mnt-backup.mount 81ms fedora-readonly.service 76ms systemd-fsck@dev-disk-by\x2duuid-f8bf87c5\x2d8cf5\x2d4998\x2da104\x2deab3b3e511f3.service 74ms ceph.service 66ms systemd-udevd.service 66ms mnt-Freedos.mount 66ms systemd-fsck@dev-disk-by\x2duuid-cbec5ef4\x2dc354\x2d40c3\x2db317\x2d0b208afa6198.service 64ms sshd.service 61ms rpc-statd-notify.service 60ms mnt-Linux-LinuxMint.mount 60ms systemd-localed.service 55ms blk-availability.service 50ms systemd-hostnamed.service 49ms systemd-user-sessions.service 49ms systemd-remount-fs.service 48ms systemd-journald.service 48ms proc-sys-fs-binfmt_misc.mount 44ms abrt-ccpp.service 44ms kmod-static-nodes.service 44ms dev-hugepages.mount 43ms NetworkManager.service 39ms mnt-Linux-Ubuntu.mount 38ms dev-disk-by\x2duuid-45a1fb95\x2d46a5\x2d4bb4\x2dac6d\x2d195aaca9734f.swap 37ms livesys-late.service 30ms tmp.mount 29ms systemd-fsck-root.service 28ms console-kit-daemon.service 28ms fedora-import-state.service 26ms var.mount 22ms wpa_supplicant.service 20ms upower.service 19ms plymouth-read-write.service 14ms sys-kernel-debug.mount 14ms systemd-random-seed.service 12ms systemd-sysctl.service 10ms sys-fs-fuse-connections.mount 9ms auditd.service 9ms nfs-config.service 9ms var-lib-nfs-rpc_pipefs.mount 7ms systemd-update-utmp.service 7ms systemd-update-utmp-runlevel.service 4ms dracut-shutdown.service 4ms dev-mqueue.mount 3ms sys-kernel-config.mount
3) cat /var/log/boot.log (si noti “[FAILED] Failed to start Network Manager Wait Online”):

[code]# cat /var/log/boot.log
OK ] Found device Crucial_CT120M500SSD1 Fedora.
OK ] Started dracut initqueue hook.
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
Starting File System Check on /dev/disk/by-uuid/78889be0-e0da-46d4-b0ae-1c839a2b79ce…
OK ] Started File System Check on /dev/disk/by-uuid/78889be0-e0da-46d4-b0ae-1c839a2b79ce.
Mounting /sysroot…
OK ] Mounted /sysroot.
OK ] Reached target Initrd Root File System.
Starting Reload Configuration from the Real Root…
OK ] Started Reload Configuration from the Real Root.
OK ] Started Show Plymouth Boot Screen.
OK ] Reached target Paths.
OK ] Reached target Basic System.
OK ] Reached target Initrd File Systems.
OK ] Reached target Initrd Default Target.
Starting dracut pre-pivot and cleanup hook…
OK ] Started dracut pre-pivot and cleanup hook.
Starting Cleaning Up and Shutting Down Daemons…
Starting Plymouth switch root service…
OK ] Stopped target Timers.
OK ] Stopped Cleaning Up and Shutting Down Daemons.
OK ] Stopped dracut pre-pivot and cleanup hook.
Stopping dracut pre-pivot and cleanup hook…
OK ] Stopped target Remote File Systems.
OK ] Stopped target Remote File Systems (Pre).
OK ] Stopped target Initrd Default Target.
OK ] Stopped target Basic System.
OK ] Stopped target Sockets.
OK ] Stopped target System Initialization.
OK ] Stopped Apply Kernel Variables.
Stopping Apply Kernel Variables…
OK ] Stopped target Swap.
Stopping udev Kernel Device Manager…
OK ] Stopped target Local File Systems.
OK ] Stopped target Paths.
OK ] Stopped target Slices.
OK ] Stopped dracut initqueue hook.
Stopping dracut initqueue hook…
OK ] Stopped udev Coldplug all Devices.
Stopping udev Coldplug all Devices…
OK ] Started Plymouth switch root service.
OK ] Stopped udev Kernel Device Manager.
OK ] Stopped Create Static Device Nodes in /dev.
Stopping Create Static Device Nodes in /dev…
OK ] Stopped Create list of required static device nodes for the current kernel.
Stopping Create list of required static device nodes for the current kernel…
OK ] Stopped dracut pre-udev hook.
Stopping dracut pre-udev hook…
OK ] Stopped dracut cmdline hook.
Stopping dracut cmdline hook…
OK ] Closed udev Kernel Socket.
OK ] Closed udev Control Socket.
Starting Cleanup udevd DB…
OK ] Started Cleanup udevd DB.
OK ] Reached target Switch Root.
Starting Switch Root…

Welcome to Fedora 23 (Workstation Edition)!

OK ] Stopped Switch Root.
OK ] Stopped Journal Service.
Starting Journal Service…
Starting Remount Root and Kernel File Systems…
Mounting Huge Pages File System…
Starting Create list of required static device nodes for the current kernel…
OK ] Reached target User and Group Name Lookups.
OK ] Set up automount Arbitrary Executable File Formats File System Automount Point.
Starting Load Kernel Modules…
Mounting Temporary Directory…
OK ] Created slice system-systemd\x2dfsck.slice.
OK ] Listening on Device-mapper event daemon FIFOs.
OK ] Listening on /dev/initctl Compatibility Named Pipe.
OK ] Stopped target Switch Root.
OK ] Stopped target Initrd Root File System.
OK ] Listening on udev Kernel Socket.
OK ] Created slice User and Session Slice.
OK ] Stopped target Initrd File Systems.
Mounting NFSD configuration filesystem…
Starting Set Up Additional Binary Formats…
Mounting Debug File System…
OK ] Created slice system-getty.slice.
OK ] Reached target Login Prompts.
OK ] Listening on LVM2 poll daemon socket.
OK ] Reached target Slices.
OK ] Listening on LVM2 metadata daemon socket.
Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling…
OK ] Listening on udev Control Socket.
Mounting POSIX Message Queue File System…
OK ] Mounted POSIX Message Queue File System.
OK ] Mounted Debug File System.
OK ] Mounted Huge Pages File System.
OK ] Mounted Temporary Directory.
OK ] Started Journal Service.
OK ] Started Remount Root and Kernel File Systems.
OK ] Started Create list of required static device nodes for the current kernel.
OK ] Started LVM2 metadata daemon.
Starting LVM2 metadata daemon…
Mounting Arbitrary Executable File Formats File System…
Starting Create Static Device Nodes in /dev…
Starting udev Coldplug all Devices…
Starting Configure read-only root support…
OK ] Mounted Arbitrary Executable File Formats File System.
OK ] Started Set Up Additional Binary Formats.
OK ] Mounted NFSD configuration filesystem.
OK ] Started Load Kernel Modules.
OK ] Started Configure read-only root support.
OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager…
OK ] Reached target Local File Systems (Pre).
Starting Apply Kernel Variables…
OK ] Started Apply Kernel Variables.
OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization…
OK ] Started udev Kernel Device Manager.
OK ] Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
OK ] Found device Crucial_CT120M500SSD1 Ubuntu.
Starting File System Check on /dev/disk/by-uuid/f8bf87c5-8cf5-4998-a104-eab3b3e511f3…
OK ] Found device Crucial_CT120M500SSD1 var.
Starting File System Check on /dev/disk/by-uuid/cbec5ef4-c354-40c3-b317-0b208afa6198…
OK ] Found device ST32000542AS backup.
Starting File System Check on /dev/disk/by-uuid/3ad6e5a2-ed64-44a0-842b-bcdb8aafe603…
OK ] Found device ST32000542AS WindowsXP64.
OK ] Found device WDC_WD20EZRX-00D8PB0 2.
OK ] Found device WDC_WD20EZRX-00D8PB0 datiWindows.
Mounting /mnt/Windows/Dati…
Activating swap /dev/disk/by-uuid/45a1fb95-46a5-4bb4-ac6d-195aaca9734f…
Mounting /mnt/Windows/XP64…
OK ] Started File System Check on /dev/disk/by-uuid/f8bf87c5-8cf5-4998-a104-eab3b3e511f3.
OK ] Started File System Check on /dev/disk/by-uuid/cbec5ef4-c354-40c3-b317-0b208afa6198.
OK ] Found device WDC_WD20EZRX-00D8PB0 home.
OK ] Activated swap /dev/disk/by-uuid/45a1fb95-46a5-4bb4-ac6d-195aaca9734f.
Starting File System Check on /dev/disk/by-uuid/438d24f3-06e2-4fa4-bc4c-3933655f9845…
OK ] Reached target Swap.
OK ] Created slice system-configure\x2dprinter.slice.
Mounting FUSE Control File System…
Mounting /var…
Mounting /mnt/Linux/Ubuntu…
OK ] Mounted FUSE Control File System.
OK ] Started File System Check on /dev/disk/by-uuid/3ad6e5a2-ed64-44a0-842b-bcdb8aafe603.
OK ] Found device WDC_WD20EZRX-00D8PB0 LinuxMint.
OK ] Found device WDC_WD20EZRX-00D8PB0 FREEDOS.
OK ] Mounted /var.
OK ] Mounted /mnt/Linux/Ubuntu.
OK ] Reached target Sound Card.
Starting Apply Ksplice updates…
Starting Load/Save Random Seed…
Starting Flush Journal to Persistent Storage…
Mounting /mnt/Freedos…
Starting File System Check on /dev/disk/by-uuid/b75c4fe9-a2e5-478b-9425-cf5b18ad8f39…
Mounting /mnt/backup…
OK ] Started Load/Save Random Seed.
OK ] Mounted /mnt/Freedos.
OK ] Mounted /mnt/backup.
OK ] Started File System Check on /dev/disk/by-uuid/438d24f3-06e2-4fa4-bc4c-3933655f9845.
Mounting /home…
OK ] Mounted /mnt/Windows/Dati.
OK ] Started File System Check on /dev/disk/by-uuid/b75c4fe9-a2e5-478b-9425-cf5b18ad8f39.
Mounting /mnt/Linux/LinuxMint…
OK ] Mounted /home.
OK ] Mounted /mnt/Windows/XP64.
OK ] Mounted /mnt/Linux/LinuxMint.
OK ] Started Apply Ksplice updates.
OK ] Started Flush Journal to Persistent Storage.
OK ] Started udev Wait for Complete Device Initialization.
Starting Activation of DM RAID sets…
OK ] Started Activation of DM RAID sets.
OK ] Reached target Encrypted Volumes.
OK ] Reached target Local File Systems.
Starting Tell Plymouth To Write Out Runtime Data…
Starting Import network configuration from initramfs…
Starting Preprocess NFS configuration…
Starting Restore /run/initramfs on shutdown…
OK ] Started Restore /run/initramfs on shutdown.
OK ] Started Preprocess NFS configuration.
OK ] Started Tell Plymouth To Write Out Runtime Data.
OK ] Started Import network configuration from initramfs.
Starting Create Volatile Files and Directories…
OK ] Started Create Volatile Files and Directories.
Mounting RPC Pipe File System…
Starting Security Auditing Service…
OK ] Mounted RPC Pipe File System.
OK ] Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown…
OK ] Started Update UTMP about System Boot/Shutdown.
OK ] Reached target System Initialization.
OK ] Listening on ACPID Listen Socket.
OK ] Listening on PC/SC Smart Card Daemon Activation Socket.
OK ] Listening on Open-iSCSI iscsiuio Socket.
OK ] Listening on Open-iSCSI iscsid Socket.
OK ] Listening on RPCbind Server Activation Socket.
Starting Console System Startup Logging…
OK ] Listening on D-Bus System Message Bus Socket.
OK ] Reached target Timers.
OK ] Reached target Paths.
OK ] Listening on CUPS Scheduler.
OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
OK ] Reached target Sockets.
OK ] Reached target Basic System.
Starting IIO Sensor Proxy service…
Starting Login Service…
OK ] Started D-Bus System Message Bus.
Starting D-Bus System Message Bus…
Starting LSB: Init script for live image…
Starting System Logging Service…
OK ] Started Hardware RNG Entropy Gatherer Daemon.
Starting Hardware RNG Entropy Gatherer Daemon…
Starting Console Mouse manager…
Starting Machine Check Exception Logging Daemon…
OK ] Started Configure Plugged-In Printer.
Starting Configure Plugged-In Printer…
OK ] Started irqbalance daemon.
Starting irqbalance daemon…
Starting Rollback uncommitted netcf network config change transactions…
Starting NTP client/server…
Starting Restorecon maintaining path file context…
Starting Accounts Service…
OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting Self Monitoring and Reporting Technology (SMART) Daemon…
Starting RealtimeKit Scheduling Policy Service…
Starting Avahi mDNS/DNS-SD Stack…
Starting Hardware Monitoring Sensors…
Starting GSSAPI Proxy Daemon…
Starting firewalld - dynamic firewall daemon…
OK ] Started Manage Sound Card State (restore and store).
Starting Manage Sound Card State (restore and store)…
OK ] Started System Logging Service.
OK ] Started Console System Startup Logging.
OK ] Started IIO Sensor Proxy service.
OK ] Started LSB: Init script for live image…
OK ] Started Console Mouse manager.
OK ] Started Machine Check Exception Logging Daemon.
OK ] Started Rollback uncommitted netcf network config change transactions.
OK ] Started Restorecon maintaining path file context.
OK ] Started GSSAPI Proxy Daemon.
OK ] Started NTP client/server.
OK ] Started Hardware Monitoring Sensors.
OK ] Started RealtimeKit Scheduling Policy Service.
OK ] Started Avahi mDNS/DNS-SD Stack.
OK ] Started Login Service.
Starting Authorization Manager…
OK ] Reached target NFS client services.
Starting ABRT Automated Bug Reporting Tool…
OK ] Started Authorization Manager.
OK ] Started Accounts Service.
OK ] Started firewalld - dynamic firewall daemon.
Starting Network Manager…
OK ] Started Network Manager.
Starting Network Manager Wait Online…
Starting Network Manager Script Dispatcher Service…
OK ] Started Network Manager Script Dispatcher Service.
OK ] Started ABRT Automated Bug Reporting Tool.
OK ] Started ABRT kernel log watcher.
Starting ABRT kernel log watcher…
OK ] Started ABRT Xorg log watcher.
Starting ABRT Xorg log watcher…
Starting Install ABRT coredump hook…
OK ] Started Install ABRT coredump hook.
[FAILED] Failed to start Network Manager Wait Online.
See ‘systemctl status NetworkManager-wait-online.service’ for details.
OK ] Reached target Network.
Starting Notify NFS peers of a restart…
Starting Samba SMB Daemon…
Starting OpenSSH server daemon…
Starting Berkeley Open Infrastructure Network Computing Client…
Starting MariaDB 10.0 database server…
OK ] Reached target Network is Online.
Starting Prefetch new Ksplice updates…
OK ] Started Logout off all iSCSI sessions on shutdown.
Starting Logout off all iSCSI sessions on shutdown…
Starting Availability of block devices…
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
Starting LSB: Start Ceph distributed file system daemons at boot time…
Starting Permit User Sessions…
Starting A Perl Client Used To Update Dynamic DNS…
Starting Virtualization daemon…
Starting CUPS Scheduler…
OK ] Started Notify NFS peers of a restart.
OK ] Started OpenSSH server daemon.
OK ] Started Availability of block devices.
OK ] Started Permit User Sessions.
OK ] Started LSB: Start Ceph distributed file system daemons at boot time.
Starting Manage, Install and Generate Color Profiles…
Starting SYSV: Late init script for live image…
OK ] Started Job spooling tools.
Starting Job spooling tools…
OK ] Started Command Scheduler.
Starting Command Scheduler…
Starting Wait for Plymouth Boot Screen to Quit…
Starting GNOME Display Manager…
OK ] Started SYSV: Late init script for live image…[/code]
4) systemctl status NetworkManager-wait-online.service -l:

[code]$ systemctl status NetworkManager-wait-online.service -l
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since mar 2016-04-12 11:06:43 CEST; 1min 30s ago
Process: 1102 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited, status=1/FAILURE)
Main PID: 1102 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.[/code]
5) systemctl status plymouth-quit-wait.service -l (visto il tempo impiegato da plymouth-quit-wait.service):

[code]$ systemctl status plymouth-quit-wait.service -l
● plymouth-quit-wait.service - Wait for Plymouth Boot Screen to Quit
Loaded: loaded (/usr/lib/systemd/system/plymouth-quit-wait.service; disabled; vendor preset: disabled)
Active: inactive (dead) since mar 2016-04-12 11:07:04 CEST; 12min ago
Process: 1412 ExecStart=/usr/bin/plymouth --wait (code=exited, status=0/SUCCESS)
Main PID: 1412 (code=exited, status=0/SUCCESS)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.[/code]
6) cat /etc/default/grub:

$ cat /etc/default/grub (ho tolto "quiet splash"): GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=false GRUB_CMDLINE_LINUX="vconsole.font=latarcyrheb-sun16 vconsole.keymap=it rd.lvm=0 rd.luks=0" GRUB_GFXMODE=1280x1024x32 GRUB_GFXPAYLOAD_LINUX=1280x1024x32 GRUB_BACKGROUND=/boot/VenereSuSole06062012.jpg GRUB_TERMINAL_OUTPUT=gfxterm

Ho provato a disinstallare plymouth:

# dnf history info last ID transazione : 1275 Ora inizio : Tue Apr 12 11:28:33 2016 rpmdb iniziale : 5485:cd68deef49733d532b04369bf2525ca8273de1ee Ora termine : 11:28:36 2016 (3 secondi) rpmdb finale : 5476:c9eaff5e85ee35af6e41627136004e42b6638159 Utente : marco <marco> Return-Code : Completato Linea di comando : remove plymouth-system-theme-0.8.9-11.2013.08.14.fc23.x86_64 plymouth-plugin-label-0.8.9-11.2013.08.14.fc23.x86_64 plymouth-scripts-0.8.9-11.2013.08.14.fc23.x86_64 plymouth-plugin-two-step-0.8.9-11.2013.08.14.fc23.x86_64 plymouth-core-libs-0.8.9-11.2013.08.14.fc23.x86_64 fedup-dracut-plymouth-0.9.2-3.fc23.noarch plymouth-graphics-libs-0.8.9-11.2013.08.14.fc23.x86_64 plymouth-theme-charge-0.8.9-11.2013.08.14.fc23.x86_64 plymouth-0.8.9-11.2013.08.14.fc23.x86_64 Transazione eseguita con: Installato dnf-1.1.7-2.fc23.noarch @updates Installato rpm-4.13.0-0.rc1.12.fc23.x86_64 @updates Pacchetti modificati: Eliminato fedup-dracut-plymouth-0.9.2-3.fc23.noarch @updates Eliminato plymouth-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-core-libs-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-graphics-libs-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-plugin-label-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-plugin-two-step-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-scripts-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-system-theme-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Eliminato plymouth-theme-charge-0.8.9-11.2013.08.14.fc23.x86_64 @@commandline Output della scriptlet: 1 avvertimento: /etc/plymouth/plymouthd.conf salvato come /etc/plymouth/plymouthd.conf.rpmsave

Ma il risultato non è cambiato:

[code]$ systemctl status NetworkManager-wait-online.service -l
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since mar 2016-04-12 11:29:47 CEST; 3min 21s ago
Process: 1097 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited, status=1/FAILURE)
Main PID: 1097 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.[/code]

$ systemd-analyze blame 30.099s NetworkManager-wait-online.service 6.330s uptrack-prefetch.service 2.879s abrtd.service 2.848s plymouth-start.service 1.548s mariadb.service [cut]
Edit: visto lo strano (avendo rimosso plymouth) “2.848s plymouth-start.service”, ho ricreato il Ram Disk Iniziale:

# dracut -f /boot/initramfs-$(uname -r).img $(uname -r)

ma il risultato non è cambiato nella sostanza:

$ systemd-analyze blame 30.099s NetworkManager-wait-online.service 7.222s uptrack-prefetch.service 2.835s abrtd.service 1.738s systemd-udev-settle.service 1.540s mariadb.service 1.029s boinc-client.service [cut]

Ciao Marco.
Il problema è senza dubbio interessante. Vediamo se da questi output emerge qualcosa:

$ cat /usr/lib/systemd/system/NetworkManager-wait-online.service
$ systemd-analyze critical-chain NetworkManager-wait-online.service
# journalctl -b 0 -u NetworkManager.service

[code]$ cat /usr/lib/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Requisite=NetworkManager.service
After=NetworkManager.service
Wants=network.target
Before=network.target network-online.target

[Service]
Type=oneshot
ExecStart=/usr/bin/nm-online -s -q --timeout=30

[Install]
WantedBy=multi-user.target[/code]

[code]$ systemd-analyze critical-chain NetworkManager-wait-online.service
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

NetworkManager-wait-online.service +30.086s
└─NetworkManager.service @3.789s +45ms
└─firewalld.service @2.867s +908ms
└─polkit.service @3.007s +124ms
└─basic.target @2.709s
└─sockets.target @2.709s
└─cups.socket @2.709s
└─sysinit.target @2.686s
└─systemd-update-utmp.service @2.680s +6ms
└─auditd.service @2.639s +26ms
└─systemd-tmpfiles-setup.service @2.528s +98ms
└─fedora-import-state.service @2.490s +25ms
└─local-fs.target @2.476s
└─run-user-1000-gvfs.mount @36.141s
└─run-user-1000.mount @34.586s
└─local-fs-pre.target @596ms
└─systemd-tmpfiles-setup-dev.service @535ms +45ms
└─kmod-static-nodes.service @375ms +34ms
└─system.slice
└─-.slice[/code]

# journalctl -b 0 -u NetworkManager.service -- Logs begin at lun 2015-11-23 14:50:58 CET, end at ven 2016-05-06 14:03:44 CEST. -- mag 06 13:57:45 localhost.localdomain systemd[1]: Starting Network Manager... mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> NetworkManager (version 1.0.12-2.fc23) is starting... mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Read config: /etc/NetworkManager/NetworkManager.conf and conf.d: 10-ibft-plugin.conf, 20-connectivity-fedora.conf mag 06 13:57:45 localhost.localdomain systemd[1]: Started Network Manager. mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded settings plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded settings plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp5s2 (d9b41119-64ef-4c7c-ab8a-9cfc6103bdc8,"ADSL") mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp3s0 (4fa374c9-837a-47e3-8cbe-1f1a2d69eac8,"Switch") mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.iodine mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.openconnect mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.l2tp mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> VPN: loaded org.freedesktop.NetworkManager.openswan mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> monitoring kernel firmware directory '/lib/firmware'. mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> DNS: /etc/resolv.conf is immutable; not managing mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMVxlanFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMVlanFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMVethFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMTunFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMMacvlanFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMInfinibandFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMGreFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMEthernetFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMBridgeFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMBondFactory (internal) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> WiFi enabled by radio killswitch; enabled by state file mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> WWAN enabled by radio killswitch; enabled by state file mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> WiMAX enabled by radio killswitch; enabled by state file mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> Networking is enabled by state file mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> (lo): link connected mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): new Ethernet device (carrier: OFF, driver: 'sky2', ifindex: 3) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): new Ethernet device (carrier: OFF, driver: 'skge', ifindex: 2) mag 06 13:57:45 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): link connected mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> Auto-activating connection 'ADSL'. mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): Activation: starting connection 'ADSL' (d9b41119-64ef-4c7c-ab8a-9cfc6103bdc8) mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> NetworkManager state is now CONNECTING mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: prepare -> config (reason 'none') [40 50 0] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: config -> ip-config (reason 'none') [50 70 0] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: ip-config -> ip-check (reason 'none') [70 80 0] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: ip-check -> secondaries (reason 'none') [80 90 0] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> NetworkManager state is now CONNECTED_LOCAL mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> NetworkManager state is now CONNECTED_SITE mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> Policy set 'ADSL' (enp5s2) as default for IPv4 routing and DNS. mag 06 13:57:47 localhost.localdomain NetworkManager[1044]: <info> (enp5s2): Activation: successful, device activated. mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): link connected mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> Auto-activating connection 'Switch'. mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): Activation: starting connection 'Switch' (4fa374c9-837a-47e3-8cbe-1f1a2d69eac8) mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: prepare -> config (reason 'none') [40 50 0] mag 06 13:57:48 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] mag 06 13:57:49 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] mag 06 13:57:49 localhost.localdomain NetworkManager[1044]: <info> NetworkManager state is now CONNECTED_GLOBAL mag 06 13:58:16 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] mag 06 13:58:16 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 06 13:58:16 localhost.localdomain NetworkManager[1044]: <info> (enp3s0): Activation: successful, device activated. mag 06 13:58:16 localhost.localdomain NetworkManager[1044]: <info> startup complete mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 4) mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 5) mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): bridge port virbr0-nic was attached mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): enslaved to virbr0 mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): link connected mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> ifcfg-rh: add connection in-memory (2ba0fc84-6070-43f7-b295-3f9a11e17e02,"virbr0") mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): Activation: starting connection 'virbr0' (2ba0fc84-6070-43f7-b295-3f9a11e17e02) mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: prepare -> config (reason 'none') [40 50 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> keyfile: add connection in-memory (2f948a76-704d-4e53-9c0a-8976b31cf411,"virbr0-nic") mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): Activation: starting connection 'virbr0-nic' (2f948a76-704d-4e53-9c0a-8976b31cf411) mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: config -> ip-config (reason 'none') [50 70 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: prepare -> config (reason 'none') [40 50 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: config -> ip-config (reason 'none') [50 70 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: ip-config -> secondaries (reason 'none') [70 90 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): Activation: successful, device activated. mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0): Activation: successful, device activated. mag 06 13:58:17 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): link disconnected (deferring action for 4 seconds) mag 06 13:58:21 localhost.localdomain NetworkManager[1044]: <info> (virbr0-nic): link disconnected (calling deferred action)

Mi insospettisce quella connessione “ADSL” che corrisponde al http://forum.fedoraonline.it/viewtopic.php?id=23831 che avevo usato per qualche giorno quando si è rotto il vecchio router, prima che mi spedissero quello nuovo…

Edit: come non detto, ho sbagliato: ADSL è il nome della connessione relativa alla scheda di rete collegata con il router…

Se si hanno dei servizi che non riescono ad avviarsi correttamente, se vengono avviati prima della rete, è consigliabile usare il servizio “NetworkManager-wait-online.service”, ma googlando sembra che, in linea generale, non dovrebbe essere quasi mai necessario.
Ti chiedo:
Se fermi il servizio “NetworkManager-wait-online.service” e lo disabiliti al boot, il sistema ha dei comportamenti strani?
Ho due sistemi con due distro e il servizio di cui sopra è disabilitato e tutto funzione regolarmente, con tempi di avvio accettabili. :slight_smile:
Ciao.
Sergio

Anche a me è disabilitato: ma viene richiamato automaticamente lo stesso (forse da NetworkManager stesso?):

[code]$ systemctl status -l NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since ven 2016-05-06 13:58:16 CEST; 21min ago
Process: 1059 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited, status=1/FAILURE)
Main PID: 1059 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.[/code]

Se le cose stanno così, forse il problema sta in questo valore del timeout:

[Service] ............ ExecStart=/usr/bin/nm-online -s -q --timeout=30
riportato nel file “/usr/lib/systemd/system/NetworkManager-wait-online.service”, che è troppo basso.
Prova a scrivere “60” o più.
Ciao.
Sergio

Scherzi? Così ci metto altri 30 secondi per poter accedere alla Scrivania?
Semmai, ce ne metterei 15… L’errore non mi sembra che generi problemi (e se avvio il servizio a boot completato, ovviamente non fallisce).
L’unico problema pratico è il ritardo nel completamento del boot.

Credo ci siano uno o più servizi che hanno bisogno della rete, ma vengono avviati prima di essa. NetworkManager-wait-online.service serve a questo; a lasciarli in uno stato di “limbo temporaneo”, per un certo lasso di tempo, in modo da dare il tempo alla rete di partire.
Se NetworkManager-wait-online.service fallisce, è perché il computer non raggiunge la rete prima che sia trascorso il periodo di esistenza del limbo (appunto quei 30 secondi di timeout).

Aumentando il lasso di tempo, magari impediamo a “NetworkManager-wait-online.service” di fallire, ma sono d’accordo con Marco: non credo riduciamo il tempo di boot. Dobbiamo capire chi o cosa rallenta il processo di connessione.

Potrei esser fuori strada, ma mi pare che l’interfaccia di rete “enp3s0” sia più lenta ad attivarsi, rispetto a “enp5s2”. E guarda caso, i 30 secondi che mancano all’appello, ricadono proprio qui:

mag 06 13:57:49 localhost.localdomain NetworkManager[1044]: <info>  NetworkManager state is now CONNECTED_GLOBAL
mag 06 13:58:16 localhost.localdomain NetworkManager[1044]: <info>  (enp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Inoltre… Nel log ho pure letto un “driver: ‘sky2’”, il che mi fa venire in mente alcuni http://forum.fedoraonline.it/viewtopic.php?id=24230 da parte del driver in questione.
Per questo, se assecondiamo questa mia teoria, i seguenti output potrebbero essere utili:

# inxi -n
# ethtool enp3s0

# inxi -n Network: Card-1: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: xx:xx:xx:xx:xx:xx Card-2: Marvell 88E8001 Gigabit Ethernet Controller driver: skge IF: enp5s2 state: up speed: 100 Mbps duplex: full mac: xx:xx:xx:xx:xx:xx
(ho oscurato i MAC address)

# ethtool enp3s0 Settings for enp3s0: Supported ports: TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pg Wake-on: d Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: yes

Aggiungo che la scheda di rete enp3s0 non è connessa ad Internet: ip fisso (xxx.xxx.0.x), nessun gateway, è collegata ad uno switch e la uso solo per lo scambio veloce di files tra i computer in casa. Al contrario, l’altra scheda di rete (sempre ip fisso: xxx.xxx.1.x) è collegata al router che fa da gateway. Entrambe hanno come netmask 255.255.255.0.

Prova il seguente:

# echo 'ETHTOOL_OPTS="autoneg off speed 1000 duplex full"' >> /etc/sysconfig/network-scripts/ifcfg-enp3s0

La situazione migliora?

# journalctl -b 0 -u NetworkManager.service

Stesso tempo di avvio, stesso errore.

# journalctl -b 0 -u NetworkManager.service -- Logs begin at lun 2015-11-23 14:50:58 CET, end at dom 2016-05-08 08:37:56 CEST. -- mag 08 08:35:01 localhost.localdomain systemd[1]: Starting Network Manager... mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> NetworkManager (version 1.0.12-2.fc23) is starting... mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Read config: /etc/NetworkManager/NetworkManager.conf and conf.d: 10-ibft-plugin.conf, 20-connectivity-fedora.conf mag 08 08:35:01 localhost.localdomain systemd[1]: Started Network Manager. mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded settings plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded settings plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp3s0 (4fa374c9-837a-47e3-8cbe-1f1a2d69eac8,"Switch") mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp5s2 (d9b41119-64ef-4c7c-ab8a-9cfc6103bdc8,"ADSL") mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.iodine mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.openconnect mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.l2tp mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> VPN: loaded org.freedesktop.NetworkManager.openswan mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> monitoring kernel firmware directory '/lib/firmware'. mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> DNS: /etc/resolv.conf is immutable; not managing mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMVxlanFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMVlanFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMVethFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMTunFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMMacvlanFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMInfinibandFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMGreFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMEthernetFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMBridgeFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMBondFactory (internal) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> WiFi enabled by radio killswitch; enabled by state file mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> WWAN enabled by radio killswitch; enabled by state file mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> WiMAX enabled by radio killswitch; enabled by state file mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> Networking is enabled by state file mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> (lo): link connected mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): new Ethernet device (carrier: OFF, driver: 'sky2', ifindex: 3) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): new Ethernet device (carrier: OFF, driver: 'skge', ifindex: 2) mag 08 08:35:01 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): link connected mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> Auto-activating connection 'ADSL'. mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): Activation: starting connection 'ADSL' (d9b41119-64ef-4c7c-ab8a-9cfc6103bdc8) mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> NetworkManager state is now CONNECTING mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: prepare -> config (reason 'none') [40 50 0] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: config -> ip-config (reason 'none') [50 70 0] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: ip-config -> ip-check (reason 'none') [70 80 0] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: ip-check -> secondaries (reason 'none') [80 90 0] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> NetworkManager state is now CONNECTED_LOCAL mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> NetworkManager state is now CONNECTED_SITE mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> Policy set 'ADSL' (enp5s2) as default for IPv4 routing and DNS. mag 08 08:35:03 localhost.localdomain NetworkManager[1042]: <info> (enp5s2): Activation: successful, device activated. mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): link connected mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> Auto-activating connection 'Switch'. mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): Activation: starting connection 'Switch' (4fa374c9-837a-47e3-8cbe-1f1a2d69eac8) mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: prepare -> config (reason 'none') [40 50 0] mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: config -> ip-config (reason 'none') [50 70 0] mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] mag 08 08:35:04 localhost.localdomain NetworkManager[1042]: <info> NetworkManager state is now CONNECTED_GLOBAL mag 08 08:35:31 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] mag 08 08:35:31 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 08 08:35:31 localhost.localdomain NetworkManager[1042]: <info> (enp3s0): Activation: successful, device activated. mag 08 08:35:31 localhost.localdomain NetworkManager[1042]: <info> startup complete mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 4) mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 5) mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): bridge port virbr0-nic was attached mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): enslaved to virbr0 mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): link connected mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> ifcfg-rh: add connection in-memory (e92251e6-9316-4dfc-8eb9-daeb3cce618e,"virbr0") mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): Activation: starting connection 'virbr0' (e92251e6-9316-4dfc-8eb9-daeb3cce618e) mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: prepare -> config (reason 'none') [40 50 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> keyfile: add connection in-memory (2f8a2d84-8dc6-42bb-84a3-c90e87ec761a,"virbr0-nic") mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): Activation: starting connection 'virbr0-nic' (2f8a2d84-8dc6-42bb-84a3-c90e87ec761a) mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: config -> ip-config (reason 'none') [50 70 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: disconnected -> prepare (reason 'none') [30 40 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: prepare -> config (reason 'none') [40 50 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: config -> ip-config (reason 'none') [50 70 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: ip-config -> secondaries (reason 'none') [70 90 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): Activation: successful, device activated. mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] mag 08 08:35:33 localhost.localdomain NetworkManager[1042]: <info> (virbr0): device state change: secondaries -> activated (reason 'none') [90 100 0] mag 08 08:35:34 localhost.localdomain NetworkManager[1042]: <info> (virbr0): Activation: successful, device activated. mag 08 08:35:34 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): link disconnected (deferring action for 4 seconds) mag 08 08:35:37 localhost.localdomain NetworkManager[1042]: <info> (virbr0-nic): link disconnected (calling deferred action)

Edita il file “/etc/sysconfig/network-scripts/ifcfg-enp3s0”:

  1. Togli la riga relativa a ETHTOOL_OPTS, consigliata a commento #11.
  2. Modifica “ONBOOT=yes” in “ONBOOT=no”.
  3. Riavvia. Trovi miglioramenti?

Assolutamente sì.

$ systemd-analyze blame 8.297s uptrack-prefetch.service 7.166s NetworkManager-wait-online.service 2.825s abrtd.service 1.671s systemd-udev-settle.service 1.611s mariadb.service 1.063s boinc-client.service 926ms firewalld.service 677ms cups.service 570ms dev-sdc1.device 460ms lvm2-monitor.service 424ms systemd-journal-flush.service 389ms libvirtd.service 348ms [email protected] 309ms mnt-Windows-XP64.mount 308ms ddclient.service 294ms smb.service 261ms mnt-Windows-Dati.mount 258ms systemd-fsck@dev-disk-by\x2duuid-438d24f3\x2d06e2\x2d4fa4\x2dbc 241ms accounts-daemon.service 212ms uptrack.service 210ms systemd-logind.service 207ms rtkit-daemon.service 199ms avahi-daemon.service 196ms packagekit.service 195ms console-kit-log-system-start.service 170ms udisks2.service 159ms home.mount 147ms systemd-udev-trigger.service 141ms systemd-modules-load.service 134ms lm_sensors.service 134ms systemd-fsck@dev-disk-by\x2duuid-xxxxxxxxxxxxxxxxxxx 132ms systemd-vconsole-setup.service 129ms systemd-binfmt.service 127ms proc-fs-nfsd.mount 119ms var.mount 111ms mnt-Freedos.mount 110ms mnt-Linux-LinuxMint.mount 109ms netcf-transaction.service 103ms livesys.service 101ms mcelog.service 100ms gssproxy.service 99ms dmraid-activation.service 99ms restorecond.service 98ms gpm.service 96ms systemd-tmpfiles-setup.service 91ms polkit.service [cut]

Edit: ottengo risultati buoni anche lasciando la spunta su “Connettere automaticamente” e togliendola a “Rendere disponibile agli altri utenti”: probabilmente in questo modo la connessione avviene quando entro nel mio utente, impedendo a NetworkManager-wait-online di aspettarla. Non ho cronometrato i tempi per verificare il totale (quindi non potrei giurare che migliori il tempo di accesso al desktop), ma sicuramente così la connessione è attiva quando mi loggo (ho un solo utente).

Circa 30 secondi per l’accesso alla Scrivania con login automatico senza l’opzione “Rendere disponibile agli altri utenti”, contro circa 55 con l’opzione selezionata.
Visto l’uso che faccio della scheda di rete in questione (usata solo per scambiare velocemente files via cavo tra computer della mia rete interna) e la presenza di un solo utente, al momento per me va bene così.
Ovviamente, per eventuali ulteriori prove che potessero servire per capire l’origine del bug e una sua eventuale soluzione, sono qui.

N.B. Ma non sarà collegato all’assenza di un gateway per la connessione in questione?