[systemd-devel] systemd-networkd only brings up network interfaces when systemd-udevd sleeps for 5 seconds
Lennart Poettering
lennart at poettering.net
Thu May 14 09:22:32 UTC 2020
On Do, 07.05.20 10:00, deffo at gmx.de (deffo at gmx.de) wrote:
> Hi there!
>
> I'm on a Yocto system with latest v241 stable systemd. The odd thing
Latest stable systemd release is actually v245.
Consider updating, there's a good chance this already works on less
old systemd.
> is, that systemd-networkd only brings up network interfaces when
> systemd-udevd sleeps for 5 seconds at boot up.
>
> If I write the two lines
>
> [Service]
> ExecStartPost=/bin/sleep 5
>
> to /etc/systemd/system/systemd-udevd.service.d/override.conf both network interfaces enp2s0 and enp3s0 come up like a charm. If I omit the two lines in override.conf the two interfaces stay down. I attached the two logs with systemd.log_level=debug udev.log_priority=debug enabled.
>
> It's remarkable that the order of the init phase of the interfaces switches in the not working case
>
> Line 6311: May 06 10:31:23 systemd-networkd[185]: enp2s0: New device has no master, continuing without
It appears networkd picks up the device before it was processed by udev.
Lennart
--
Lennart Poettering, Berlin
More information about the systemd-devel
mailing list