Arch Linux

rochus

Member

Registered: 2007-02-14

Posts: 91

[SOLVED] systemd-networkd-wait-online.service times out

Hi,

I noticed a few days ago that on one of my systems, systemd-networkd-wait-online.service times out during boot. I noticed due to an error message when shutting down the system, as well as my vpn connections only coming up once the service timed out. This is insofar surprising as this behavior started only recently. At least I didn't notice until about 3 days ago. I tried to track the roots of the issue but haven't been lucky in solving it yet.  I believe that it is due to some interaction between iwd and systemd-networkd. I did not yet find the relevant point in the wiki. I'd be happy with any leads where to look.

FYI, journalctl output:

Sep 27 10:42:58 quantum iwd[898]: resolve-systemd: Failed to modify the DNS entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.
Sep 27 10:42:58 quantum iwd[898]: resolve-systemd: Failed to modify the domains entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.
Sep 27 10:43:07 quantum systemd-resolved[889]: Using degraded feature set TCP instead of UDP for DNS server 2620:fe::9.
Sep 27 10:43:10 quantum systemd-networkd-wait-online[796]: Timeout occurred while waiting for network connectivity.
Sep 27 10:43:10 quantum systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Sep 27 10:43:10 quantum systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Sep 27 10:43:10 quantum systemd[1]: Failed to start Wait for Network to be Configured.
Sep 27 10:43:10 quantum systemd[1]: Reached target Network is Online.

I know it's just an excerpt, and will provide a full journalctl log later.

networkctl shows wlan0 still in 'configuring' despite the fact that the connection is up and stable:

$ networkctl list  
IDX LINK   TYPE     OPERATIONAL SETUP      
  1 lo     loopback carrier     unmanaged
  2 enp7s0 ether    off         unmanaged
  3 enp6s0 ether    off         unmanaged
  5 wlan0  wlan     routable    configuring
  6 tun0   none     routable    unmanaged

systemctl status for iwd.service

$ systemctl status iwd.service
● iwd.service - Wireless service
     Loaded: loaded (/usr/lib/systemd/system/iwd.service; enabled; preset: disabled)
     Active: active (running) since Wed 2023-09-27 10:41:13 CEST; 1h 55min ago
       Docs: man:iwd(8)
             man:iwd.config(5)
             man:iwd.network(5)
             man:iwd.ap(5)
   Main PID: 898 (iwd)
      Tasks: 1 (limit: 76921)
     Memory: 2.6M
        CPU: 83ms
     CGroup: /system.slice/iwd.service
             └─898 /usr/lib/iwd/iwd

Sep 27 12:33:32 quantum iwd[898]: resolve-systemd: Failed to modify the DNS entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.

(the last line repeats with later timestamps)

for systemd-networkd-wait-online.service

systemctl status systemd-networkd-wait-online.service 
× systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/etc/systemd/system/systemd-networkd-wait-online.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-09-27 10:43:10 CEST; 1h 55min ago
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 796 ExecStart=/usr/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE)
   Main PID: 796 (code=exited, status=1/FAILURE)
        CPU: 11ms

Sep 27 10:41:12 quantum systemd[1]: Starting Wait for Network to be Configured...
Sep 27 10:43:10 quantum systemd-networkd-wait-online[796]: Timeout occurred while waiting for network connectivity.
Sep 27 10:43:10 quantum systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Sep 27 10:43:10 quantum systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Sep 27 10:43:10 quantum systemd[1]: Failed to start Wait for Network to be Configured.

iwd.conf:

[General]
EnableNetworkConfiguration=true

[Network]
EnableIPv6=true
NameResolvingService=systemd

/etc/systemd/network/wlan0.network

[Match]
Name=wlan0

[Network]
MulticastDNS=yes

While the system is usable, I'd really like to understand where this issue is coming from, and how to solve it.

Thanks!

Edit: I just checked on another system which has virtually an identical configuration. Also there, systemd-networkd-wait-online.service failed.

Last edited by rochus (2023-09-27 21:18:56)

seth

Member

Registered: 2012-09-03

Posts: 59,897

Re: [SOLVED] systemd-networkd-wait-online.service times out

Sep 27 12:33:32 quantum iwd[898]: resolve-systemd: Failed to modify the DNS entries. org.freedesktop.resolve1.LinkBusy: Link wlan0 is managed.

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

and in doubt a complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

rochus

Member

Registered: 2007-02-14

Posts: 91

Re: [SOLVED] systemd-networkd-wait-online.service times out

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
lm_sensors.service                       | multi-user.target.wants
nvidia-unload-shutdown.service           | shutdown.target.wants
openvpn-client@sphere71-v2.service       | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-resolved.service                 | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants

journalctl log is at https://0x0.st/HVOk.txt

seth

Member

Registered: 2012-09-03

Posts: 59,897

Re: [SOLVED] systemd-networkd-wait-online.service times out

Sep 27 12:56:48 quantum iwd[904]: [DHCPv4] l_dhcp_client_start:1219 Entering state: DHCP_STATE_SELECTING
Sep 27 12:56:48 quantum iwd[904]: [DHCPv4] dhcp_client_handle_offer:811 Entering state: DHCP_STATE_REQUESTING
Sep 27 12:56:48 quantum iwd[904]: [DHCPv4] dhcp_client_rx_message:915 Entering state: DHCP_STATE_BOUND
Sep 27 12:56:48 quantum iwd[904]: [DHCPv4] dhcp_client_rx_message:948 T1 expiring in 43200850 ms

Do you have https://wiki.archlinux.org/title/Iwd#En … figuration enabled?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

rochus

Member

Registered: 2007-02-14

Posts: 91

Re: [SOLVED] systemd-networkd-wait-online.service times out

Yes, see first post. And that was the right hint, thanks! I thought having this configuration without having "DHCP=yes" in the systemd network configuration would be ok. There's nothing that clearly speaks against it neither in the documentation I read, nor in the wiki. Apparently I was wrong. Disabling iwd's network configuration and setting DHCP=yes in systemd's network configuration solved the issue. Marking the thread solved.

Last edited by rochus (2023-09-27 21:20:17)