FS#34170 - [networkmanager] Failed to start Network Manager Wait Online

Attached to Project: Arch Linux
Opened by Robert Orzanna (orschiro) - Wednesday, 06 March 2013, 10:11 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 13 September 2014, 18:55 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

I enabled the Network Manager Wait Online service in order to take care of Dropbox, Insync, Crashplan and other programs that cannot establish a connection if an internet connection is not available immediately after boot. However the service fails to start.

The error log from journalctl:

NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE
Failed to start Network Manager Wait Online
Unit NetworkManger-wait-online.service entered failed state
Starting Network.
Reached target Network.

Additional info:

network-manager-applet 0.9.6.4-1
networkmanager 0.9.6.4-2


Steps to reproduce:

# systemctl enable NetworkManager-wait-online.service

The normal NetworkManager service is still enabled. Disabling it does not resolve the issue but leaves me with no internet connection at all.
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 13 September 2014, 18:55 GMT
Reason for closing:  Fixed
Additional comments about closing:  from user: Reported & fixed by upstream.
Comment by ido (ik_5) - Tuesday, 12 March 2013, 09:43 GMT
I have the same problem, but without wait.
It started after the last update of NetworkManager
Comment by Robert Orzanna (orschiro) - Tuesday, 12 March 2013, 09:45 GMT
I was able to resolve it increasing the timeout from 30 to 50 in /usr/lib/systemd/system/NetworkManager-wait-online.service.

See also: https://wiki.archlinux.org/index.php/NetworkManager#Enable_NetworkManager_Wait_Online

Thus, wouldn't it be better to increase the default value in upstream?
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 16 February 2014, 14:42 GMT
  • Field changed: Status (Assigned → Waiting on Response)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
status? upstream report?
Comment by Robert Orzanna (orschiro) - Sunday, 16 February 2014, 19:37 GMT
I found this [1] bug report from July 2013 on the Fedora bug tracker which relates to this issue. Is it wise to report it there?


[1] https://bugzilla.redhat.com/show_bug.cgi?id=837793

Loading...