Arch Linux

Ploppz

Member

Registered: 2013-09-14

Posts: 313

systemd services slow to start up

systemd-networkd systematically does not get a connection before 30-60 seconds has passed since I logged in.
Here's the output of `journalctl -u systemd-networkd`:

mars 14 00:22:32 3rlend systemd[1]: Starting Network Service...
mars 14 00:22:32 3rlend systemd-networkd[542]: Enumeration completed
mars 14 00:22:32 3rlend systemd[1]: Started Network Service.
mars 14 00:22:35 3rlend systemd-networkd[542]: enp4s0: Gained carrier
mars 14 00:22:36 3rlend systemd-networkd[542]: enp4s0: Gained IPv6LL
mars 14 00:22:37 3rlend systemd-networkd[542]: enp4s0: DHCPv4 address xxx.xxx.xxx.xxx:23 via xxx.xxx.xxx.xxx
mars 14 00:22:38 3rlend systemd-networkd[542]: enp4s0: Configured

Which hints that it's not a problem with systemd-networkd, but rather a delay in getting to starting the service? I test the connection by `ping google.com`. It also seems like mpd never starts before systemd-networkd. So this is probably a problem with systemd in general.

Please tell me what more information you need to help me.

Edit: When I booted my computer today, the last journalctl entry of systemd-networkd was from 08:54:43, but I didn't get access to internet before 8:56. The log is identical to the one posted above.

Last edited by Ploppz (2016-03-20 18:33:08)

Ploppz

Member

Registered: 2013-09-14

Posts: 313

Re: systemd services slow to start up

This is the output of `systemd-analyze critical-chain`: https://bpaste.net/show/256b4fbe5241
'systemd-analyze plot` has some very long 'Active' areas, before at the very end, network.target (.. etc) start. So they are not blocked by the Activation (bright red) of other daemons. I don't know so much about how this works so I can't really tell much more from the data.