It looks a lot like this issue: https://github.com/systemd/systemd/issues/1645
Where DHCP works, it has an ip and can sync time and other items, but the wait service isn't happy. On Wed, Jun 14, 2017 at 10:46 AM, Steve Langasek < [email protected]> wrote: > The journal shows, two minutes after the start of the wait-online job: > > Jun 14 00:11:42 bar-artful6401 systemd-networkd-wait-online[618]: Event > loop failed: Connection timed out > Jun 14 00:11:42 bar-artful6401 systemd[1]: > systemd-networkd-wait-online.service: > Main process exited, code=exited, status=1/FAILURE > Jun 14 00:11:42 bar-artful6401 systemd[1]: Failed to start Wait for > Network to be Configured. > Jun 14 00:11:42 bar-artful6401 systemd[1]: > systemd-networkd-wait-online.service: > Unit entered failed state. > Jun 14 00:11:42 bar-artful6401 systemd[1]: > systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Jun 14 00:11:43 bar-artful6401 systemd[1]: Reached target Network is > Online. > > So this sounds like a protocol/socket issue, rather than an issue with > networkd reporting wrong state of the network devices. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1697730 > > Title: > Long boot time due to systemd-networkd-wait-online.service failure > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1697730/+subscriptions > ** Bug watch added: github.com/systemd/systemd/issues #1645 https://github.com/systemd/systemd/issues/1645 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
