+++ This bug was initially created as a clone of Bug #859190 +++ Created attachment 615047 [details] /var/log/messages for 3 separate boot sequences Description of problem: NetworkManager-wait-online.service fails at boot every time. Typically at 31-32 seconds after boot, the following prints to /var/log/messages: Sep 19 17:14:03 myserver systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1 Sep 19 17:14:03 myserver systemd[1]: Unit NetworkManager-wait-online.service entered failed state. /var/log/boot.log has: Starting Network Manager Wait Online... Failed to start Network Manager Wait Online This is annoying because ypbind needs to wait for NetworkManager to come online/active before it tries to activate. This then causes a domino effect resulting in other failures (cron, etc.) Version-Release number of selected component (if applicable): NetworkManager.x86_64 1:0.9.4-6.git20120521.fc16 @updates How reproducible: Every time Steps to Reproduce: 1. systemctl enable NetworkManager-wait-online.service 2. boot 3. Actual results: Fails (see above) Expected results: Success Additional info: systemctl status NetworkManager-wait-online.service NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; enabled) Active: failed since Wed, 19 Sep 2012 17:14:03 -0500; 19h ago Main PID: 914 (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/NetworkManager-wait-online.service Server is a Dell Optiplex 390 with a Intel i5 2400 CPU with Intel H61 Express Chipset. --- Additional comment from Fedora End Of Life on 2013-01-16 08:14:32 EST --- This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping --- Additional comment from Fedora End Of Life on 2013-02-13 08:56:48 EST --- Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug still happens on F17. I am running: Installed Packages Name : NetworkManager Arch : x86_64 Epoch : 1 Version : 0.9.6.4 Release : 3.fc17 Size : 7.0 M Repo : installed From repo : updates From /var/log/boot.log: [^[[1;32m OK ^[[0m] Started Network Manager. Starting Network Manager Wait Online... [^[[1;31mFAILED^[[0m] Failed to start Network Manager Wait Online. See 'systemctl status NetworkManager-wait-online.service' for details. From /var/log/messages: Feb 12 14:49:18 myhost NetworkManager[761]: <info> NetworkManager (version 0.9.6.4-3.fc17) is starting... Feb 12 14:49:50 myhost systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1 Feb 12 14:49:50 myhost systemd[1]: Unit NetworkManager-wait-online.service entered failed state.
Hello! Same problem here: Fedora 18 x86_64 sudo systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. sudo systemctl status NetworkManager-wait-online.service NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled) Active: failed (Result: exit-code) since сб 2013-02-23 11:49:44 EET; 4h 10min ago Process: 756 ExecStart=/usr/bin/nm-online -q --timeout=30 (code=exited, status=1/FAILURE) фев 23 11:49:44 zlo systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE фев 23 11:49:44 zlo systemd[1]: Failed to start Network Manager Wait Online. фев 23 11:49:44 zlo systemd[1]: Unit NetworkManager-wait-online.service entered failed state sudo cat /var/log/messages | grep NetworkManager-wait Feb 23 11:49:44 localhost systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE Feb 23 11:49:44 localhost systemd[1]: Unit NetworkManager-wait-online.service entered failed state sudo cat /var/log/boot.log | grep Network Starting Network Manager... Thank you!
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
I'm having this problem in Fedora 20. As root $ cat /etc/redhat-release Fedora release 20 (Heisenbug) $ systemctl status status NetworkManager-wait-online.service status.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled) Active: failed (Result: exit-code) since Wed 2015-03-18 14:16:14 EDT; 2min 39s ago Process: 885 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited, status=1/FAILURE) Main PID: 885 (code=exited, status=1/FAILURE) CGroup: /system.slice/NetworkManager-wait-online.service Mar 18 14:16:14 xxx systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE Mar 18 14:16:14 xxx systemd[1]: Failed to start Network Manager Wait Online. Mar 18 14:16:14 xxx systemd[1]: Unit NetworkManager-wait-online.service entered failed state. Seems to be some sort of underlying problem with the nm-online command as $ nm-online -s Connecting. 30s ... Connecting............... 1s just counts down to 1s and then exits with a failure code yet clearly NetworkManager is running just fine $ nmcli con show NAME UUID TYPE TIMESTAMP-REAL vlan-external 6881cf12-ee2c-43dc-9087-7ff65aab540f vlan Wed 18 Mar 2015 02:20:42 PM EDT vlan-internal b1f760b7-2813-405b-84bd-3e07c6345642 vlan Wed 18 Mar 2015 02:20:42 PM EDT bridge-lxc 0124f35b-e703-4889-aa91-a79e23b30be8 bridge Wed 18 Mar 2015 02:20:42 PM EDT uplink 7b7beece-1723-4708-b6e7-3ab2de4f782f 802-3-ethernet never Cheers! -Tyson
Reporter, can you bump this to Fedora 24? I still have this problem. Unfortunately not many people are typing systemctl --state=failed in their consoles, so this bug isn't going to get many "Me too!"s.
If there is no failure if you increase the --timeout , You will have to find the root casuse of the failure. Documented some workaround here https://bugzilla.redhat.com/show_bug.cgi?id=1277257