systemd-networkd is set to start at boot, but is inactive when I check after boot
Why?
Beacuse it starts the network on boot and after that it is finished with it’s job.
If you check the status of the (enabled) systemd “systemd-networkd.service” you should see a PID mentioned – check that PID and you should see that the “networkd” Daemon is running …
- You can delve deeper and check the CPU, Memory and I/O resources the “networkd” Daemon is using …
- You can also check the systemd Journal for the entries the “networkd” service wrote, with time-stamps, during the system boot …
- You can also check, with “systemd-analyze plot > systemd-analyze_plot.svg” the SVG diagram of the complete system boot …
- You can also check “systemd” for the systemd services which “need” the “networkd” service and, the systemd services which the “networkd” service “needs” …
boven:~ # systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
boven:~ #
boven:~ # ps -ef | grep networkd
root 385 346 0 11:44 pts/0 00:00:00 grep --color=auto networkd
boven:~ #
What systemd-networkd does on my machine:
erlangen:~ # systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-05-30 06:10:37 CEST; 1 day 6h ago
Docs: man:systemd-networkd.service(8)
Main PID: 707 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
Memory: 2.0M
CGroup: /system.slice/systemd-networkd.service
└─707 /usr/lib/systemd/systemd-networkd
May 30 07:28:34 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 30 07:28:34 erlangen systemd-networkd[707]: wlan0: Configured
May 30 16:49:24 erlangen systemd-networkd[707]: wlan0: Lost carrier
May 30 16:49:24 erlangen systemd-networkd[707]: wlan0: DHCPv6 lease lost
May 30 16:49:25 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 30 16:49:25 erlangen systemd-networkd[707]: wlan0: Configured
May 31 07:07:01 erlangen systemd-networkd[707]: wlan0: Lost carrier
May 31 07:07:01 erlangen systemd-networkd[707]: wlan0: DHCPv6 lease lost
May 31 07:07:02 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 31 07:07:02 erlangen systemd-networkd[707]: wlan0: Configured
erlangen:~ #
Logs are:
erlangen:~ # journalctl -b -u systemd-networkd.service
-- Logs begin at Wed 2019-04-10 09:08:16 CEST, end at Fri 2019-05-31 12:42:29 CEST. --
May 30 06:10:37 erlangen systemd[1]: Starting Network Service...
May 30 06:10:37 erlangen systemd-networkd[707]: Enumeration completed
May 30 06:10:37 erlangen systemd[1]: Started Network Service.
May 30 06:10:37 erlangen systemd-networkd[707]: wlan0: found matching network '/etc/systemd/network/30-wireless.network', based on potentially unpredictable ifname
May 30 06:10:38 erlangen systemd-networkd[707]: wlan0: Could not bring up interface: Invalid argument
May 30 06:10:39 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 30 06:10:40 erlangen systemd-networkd[707]: wlan0: Gained IPv6LL
May 30 06:10:42 erlangen systemd-networkd[707]: wlan0: Configured
May 30 06:13:12 erlangen systemd-networkd[707]: wlan0: Lost carrier
May 30 06:13:12 erlangen systemd-networkd[707]: wlan0: DHCPv6 lease lost
May 30 06:13:13 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 30 06:13:13 erlangen systemd-networkd[707]: wlan0: Configured
May 30 07:28:33 erlangen systemd-networkd[707]: wlan0: Lost carrier
May 30 07:28:33 erlangen systemd-networkd[707]: wlan0: DHCPv6 lease lost
May 30 07:28:34 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 30 07:28:34 erlangen systemd-networkd[707]: wlan0: Configured
May 30 16:49:24 erlangen systemd-networkd[707]: wlan0: Lost carrier
May 30 16:49:24 erlangen systemd-networkd[707]: wlan0: DHCPv6 lease lost
May 30 16:49:25 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 30 16:49:25 erlangen systemd-networkd[707]: wlan0: Configured
May 31 07:07:01 erlangen systemd-networkd[707]: wlan0: Lost carrier
May 31 07:07:01 erlangen systemd-networkd[707]: wlan0: DHCPv6 lease lost
May 31 07:07:02 erlangen systemd-networkd[707]: wlan0: Gained carrier
May 31 07:07:02 erlangen systemd-networkd[707]: wlan0: Configured
erlangen:~ #
What are yours?
thank you all for answering my question. You were a real help!
I was under the impression that it needed to stay active, but I was wrong.
I will start a new post with my real problem.
That is always the best way to go lol!
It lies. systemd-networkd.service includes multiple entries in [Install] section and only one link happens to be present; but this link does not cause systemd-networkd.service to be pulled into initial transaction:
bor@localhost:/etc/systemd/system> systemctl --no-pager status systemd-networkd
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; **enabled**; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
bor@localhost:/etc/systemd/system> sudo mv dbus-org.freedesktop.network1.service /tmp/dbus-org.freedesktop.network1.service
bor@localhost:/etc/systemd/system> systemctl --no-pager status systemd-networkd
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; **disabled**; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
bor@localhost:/etc/systemd/system>
This link is part of systemd package.
bor@localhost:/etc/systemd/system> rpm -qf dbus-org.freedesktop.network1.service
systemd-234-lp151.25.7.x86_64
bor@localhost:/etc/systemd/system>
If you are concerned, open openSUSE bug report against systemd package. And if you are really concerned, open upstream issue against systemd - it should really indicate partial status in this case and provide means to list symlinks that are actually created.
Also with Leap 15.0 – ** Me too !!! ** …
Did a fresh forced install of the Leap 15.0 “systemd” package – ‘systemd-234-lp150.20.15.1.x86_64’ – the systemd “networkd” service is normally disabled on my systems …
# systemctl list-unit-files | grep -iE 'network|nm-'
dbus-org.freedesktop.network1.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.opensuse.Network.AUTO4.service enabled
dbus-org.opensuse.Network.DHCP4.service enabled
dbus-org.opensuse.Network.DHCP6.service enabled
dbus-org.opensuse.Network.Nanny.service enabled
network.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager-wait-online.service disabled
NetworkManager.service disabled
systemd-networkd-wait-online.service disabled
systemd-networkd.service enabled
systemd-networkd.socket disabled
network-online.target static
network-pre.target static
network.target static
# systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
#
This results in the following links in /etc/systemd/system/:
lrwxrwxrwx 1 root root 48 18. Feb 18:32 dbus-org.freedesktop.network1.service -> /usr/lib/systemd/system/systemd-networkd.service
lrwxrwxrwx 1 root root 57 3. Mai 09:27 dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
Looks as if, also with Leap 15.0, if Wicked is being used in place of either Network Manager or systemd’s Network daemon then, some manual disabling of the related systemd services is needed – and, possibly, in the case of systemd’s Network daemon, that service always …