On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi <th9...@googlemail.com> wrote: [...]
> × systemd-networkd-wait-online.service - Wait for Network to be Configured > Loaded: loaded > (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; > vendor preset: disabled) > Active: failed (Result: exit-code) since Sun 2021-09-05 20:22:19 > CEST; 11min ago > Docs: man:systemd-networkd-wait-online.service(8) > Main PID: 984 (code=exited, status=1/FAILURE) > Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be > Configured... > Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred > while waiting for network connectivity. > Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service: > Main process exited, code=exited, status=1/FAILURE > Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network to be > Configured. > There's your problem: systemd-networkd-wait-online.service is timing out: Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred while waiting for network connectivity. The systemd-networkd-wait-online service runs relatively early and waits for *ALL* interfaces it is aware of to be fully configured or failed[1], so it probably one of your interfaces is taking too long to be ready. Between timing out and you restarting systemd-networkd.service, the interface reaches the ready state (or fails), and systemd-networkd-wait-online.service doesn't time out anymore. By your logs, you have two ethernet interfaces: enp6s0 and enp7s0, the latter not in use. Do you .network files in /etc/systemd/network/ or /run/systemd/network/? Any changes (uncommented lines) in /etc/systemd/networkd.conf? Regards. [1] https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
