systemd-networkd does not start at boot time but successfully starts after. How to fix?

S

sElijah2017-03-02 17:59:56

linux

sElijah, 2017-03-02 17:59:56

Hello.
Linux debian 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 GNU/Linux (Debian SID)
systemd 232
The essence of the problem.
in the process of loading the OS in the boot log, I observe messages:

systemd-networkd[992]: Could not connect to bus: Permission denied

After booting the system on the command:
systemctl status systemd-networkd
I make sure that the service is not running. However, nothing prevents it from starting manually:
systemctl start systemd-networkd
this time there are no errors and the network starts up. I searched for a long time for a solution to the problem, but I did not find anything.

$ ls /etc/systemd/network/
wireless-dhcp.network

$ cat /etc/systemd/network/wireless-dhcp.network
[Match]
Name=wlp4s0

[Network]
DHCP=yes

$ cat /etc/wpa_supplicant/wpa_supplicant-wlp4s0.conf 
network={
        ssid="SSID"
        #psk="PSK-Key"
        psk=PskKey
}

systemctl list-unit-files |grep enabled
accounts-daemon.service                                                enabled  
atd.service                                                            enabled  
[email protected]                                                        enabled  
avahi-daemon.service                                                   enabled  
binfmt-support.service                                                 enabled  
bluetooth.service                                                      enabled  
console-setup.service                                                  enabled  
cron.service                                                           enabled  
dbus-org.bluez.service                                                 enabled  
dbus-org.freedesktop.Avahi.service                                     enabled  
dbus-org.freedesktop.network1.service                                  enabled  
dbus-org.freedesktop.resolve1.service                                  enabled  
display-manager.service                                                enabled  
[email protected]                                                         enabled  
keyboard-setup.service                                                 enabled  
lm-sensors.service                                                     enabled  
rsyslog.service                                                        enabled  
slim.service                                                           enabled  
smartd.service                                                         enabled  
smartmontools.service                                                  enabled  
syslog.service                                                         enabled  
systemd-networkd.service                                               enabled  
systemd-resolved.service                                               enabled  
systemd-timesyncd.service                                              enabled  
unattended-upgrades.service                                            enabled  
[email protected]                                                enabled  
avahi-daemon.socket                                                    enabled  
systemd-networkd.socket                                                enabled  
uuidd.socket                                                           enabled  
machines.target                                                        enabled  
remote-fs.target                                                       enabled  
apt-daily.timer                                                        enabled

Didn't touch anything here.

$ ls /lib/systemd/network/
80-container-host0.network  80-container-ve.network  80-container-vz.network  99-default.link

Manually, the network normally starts and works. At the stage of loading - no. What can be wrong?

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

A

Alexey Timofeev, 2017-03-09
@alextimofeyev7

Remove systemd, it often has such adventures
without-systemd.org/wiki/index.php/How_to_remove_s...

S

sElijah, 2017-03-09
@sElijah

That doesn't work: the only problem with systemd is this, and that, it's local. A clean installation of the system is devoid of it. I would like to solve it for the current one. Perhaps some error in the configs, because the system has been installed since the release of Debian Lenny. I didn’t clean up anything in particular - I updated it according to releases, and by the time Wheezy was released, he switched to the SID branch. The problem is not in the distribution - I checked a clean installation of the same distribution.
Also, I wouldn't want to mess around with finding replacements/configuring nspawn containers.