Since upgrade from systemd-210-3 to 211 I see this log error on journal This is running networkd with loglevel debug: ---- # journalctl -b -u systemd-networkd.service -- Logs begin at Sun 2014-03-09 19:07:02 ART, end at Wed 2014-03-12 01:23:37 ART. -- Mar 12 01:23:24 archbase systemd[1]: Starting Network Service... Mar 12 01:23:24 archbase systemd-networkd[147]: timestamp of '/etc/systemd/network' changed Mar 12 01:23:24 archbase systemd-networkd[147]: timestamp of '/usr/lib/systemd/network' changed Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: found matching network '/etc/systemd/network/ens3.network' Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: requesting link status Mar 12 01:23:24 archbase systemd-networkd[147]: Failed to save link data /run/systemd/network/links/2: No such file or directory Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: bringing link up Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: link (with ifindex 2) added Mar 12 01:23:24 archbase systemd-networkd[147]: lo: link (with ifindex 1) added Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: MAC address: 52:54:00:12:34:56 Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: link status updated: 00000000 -> 0x00001002 Mar 12 01:23:24 archbase systemd-networkd[147]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_c Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: MAC address: 52:54:00:12:34:56 Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: link is up Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: carrier on Mar 12 01:23:24 archbase systemd-networkd[147]: DHCP CLIENT: set MAC address to 52:54:00:12:34:56 Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: acquiring DHCPv4 lease Mar 12 01:23:24 archbase systemd-networkd[147]: DHCP CLIENT: STARTED Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: link status updated: 0x00001002 -> 0x00011043 Mar 12 01:23:24 archbase systemd-networkd[147]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.2 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a Mar 12 01:23:24 archbase systemd-networkd[147]: DHCP CLIENT: DISCOVER Mar 12 01:23:24 archbase systemd-networkd[147]: Got message type=signal sender=org.freedesktop.DBus destination=:1.2 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply Mar 12 01:23:24 archbase systemd[1]: Started Network Service. Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: link already exists, ignoring Mar 12 01:23:24 archbase systemd-networkd[147]: DHCP CLIENT: OFFER Mar 12 01:23:24 archbase systemd-networkd[147]: ens3: link already exists, ignoring Mar 12 01:23:24 archbase systemd-networkd[147]: DHCP CLIENT: REQUEST Mar 12 01:23:25 archbase systemd-networkd[147]: DHCP CLIENT: REQUEST Mar 12 01:23:26 archbase systemd-networkd[147]: DHCP CLIENT: ACK Mar 12 01:23:26 archbase systemd-networkd[147]: ens3: DHCPv4 address 192.168.0.218/24 via 192.168.0.1 Mar 12 01:23:26 archbase systemd-networkd[147]: Setting transient hostname: 'host322' Mar 12 01:23:26 archbase systemd-networkd[147]: Sent message type=method_call sender=n/a destination=org.freedesktop.hostname1 object=/org/freedesktop/hostname1 interface=org.freedesktop.hostname1 member=SetHost Mar 12 01:23:26 archbase systemd-networkd[147]: ens3: setting addresses Mar 12 01:23:26 archbase systemd-networkd[147]: ens3: addresses set Mar 12 01:23:26 archbase systemd-networkd[147]: ens3: setting routes Mar 12 01:23:26 archbase systemd-networkd[147]: ens3: routes set Mar 12 01:23:26 archbase systemd-networkd[147]: ens3: link configured Mar 12 01:23:26 host322 systemd-networkd[147]: Got message type=method_return sender=:1.3 destination=:1.2 object=n/a interface=n/a member=n/a cookie=4 reply_cookie=2 error=n/a # ---- ---- # cat /etc/systemd/network/ens3.network [Match] Name=ens3 [Network] DHCP=true # ---- This also happens when on a basic static network config. Running Arch Linux (x86_64)
This was fixed for me in 212
Yes, seems to be fixed in 212
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.