Arch Linux

bartbart2003

Member

Registered: 2021-04-03

Posts: 2

systemd-networkd fails to start

Hello, I installed Arch Linux today, and now I have a problem with setting up the network - systemd-networkd fails to start. I don't think I've installed anything network-related, I don't have dhcpcd installed. I have a wired connection (which is visible by the system and ping 8.8.8.8 works, although ping google.com gives "System error"). What am I doing wrong?

× systemd-networkd.service - Network Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2021-04-03 19:45:32 CEST; 1min 58s ago
TriggeredBy: × systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
    Process: 348 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=200/CHDIR)
   Main PID: 348 (code=exited, status=200/CHDIR)
        CPU: 9ms

Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: systemd-networkd fails to start

ping 8.8.8.8 works, although ping google.com gives "System error"

https://bbs.archlinux.org/viewtopic.php?id=57855

Can we also see the full content of the systemd-networkd configuration files and the output of

cat /etc/{nsswitch,resolv}.conf
ls -lR /etc/systemd/system
journalctl -u systemd-networkd
networkctl status

---

Jin, Jîyan, Azadî

bartbart2003

Member

Registered: 2021-04-03

Posts: 2

Re: systemd-networkd fails to start

To add a little more context: first I tried to install dhcpcd. It kind of worked (I mean, /etc/resolv.conf got populated with correct DNS addresses and I could ping 8.8.8.8 for example), but if I tried to ping a domain name like archlinux.org it instantly returned something like "ping: archlinux.org: System error" (yeah, that's it, one line of output, nothing more). After a bit of googling I uninstalled dhcpcd and tried to setup my network connection using the pre-installed systemd-networkd and systemd-resolved. The problem is... it turned out neither of those start correctly (both give the same "status=200/CHDIR" message). I also booted the live system from USB and checked the output of the systemctl status command there, and they're both running fine and I have a network connection out of the box. Is there something I'm missing? Maybe I have accidentally modified something while playing around with the network config... Also, is networkd the right choice for me (desktop PC, wired connection, DHCP, nothing fancy)? Or should I use NetworkManager instead? Oh and my networkd config file looks pretty much like the "Wired adapter using DHCP" example from the wiki (I only changed the device name).

cat /etc/nsswitch.conf (resolv.conf didn't exist when I ran this command but even when it was there it didn't change anything)

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files

publickey: files

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

ls -lR /etc/systemd/system

/etc/systemd/system:
total 8
drwxr-xr-x 2 root root 4096 Apr  3 15:07 getty.target.wants
drwxr-xr-x 2 root root 4096 Apr  3 19:42 multi-user.target.wants

/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Apr  3 15:07 getty@tty1.service -> /usr/lib/systemd/system/getty@.service

/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Apr  3 15:07 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target

journalctl -u systemd-networkd

Apr 03 19:45:32 bartbart2003-arch systemd[1]: Starting Network Service...
Apr 03 19:45:32 bartbart2003-arch systemd[344]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Starting Network Service...
Apr 03 19:45:32 bartbart2003-arch systemd[345]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 2.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Starting Network Service...
Apr 03 19:45:32 bartbart2003-arch systemd[346]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 3.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Starting Network Service...
Apr 03 19:45:32 bartbart2003-arch systemd[347]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Starting Network Service...
Apr 03 19:45:32 bartbart2003-arch systemd[348]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 19:45:32 bartbart2003-arch systemd[1]: Failed to start Network Service.

networkctl status

● State: n/a

Apr 03 21:29:40 bartbart2003-arch systemd[1]: Starting Network Service...
Apr 03 21:29:40 bartbart2003-arch systemd[342]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 03 21:29:40 bartbart2003-arch systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Apr 03 21:29:40 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 21:29:40 bartbart2003-arch systemd[1]: Failed to start Network Service.
Apr 03 21:29:40 bartbart2003-arch systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Apr 03 21:29:40 bartbart2003-arch systemd[1]: Stopped Network Service.
Apr 03 21:29:40 bartbart2003-arch systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Apr 03 21:29:40 bartbart2003-arch systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Apr 03 21:29:40 bartbart2003-arch systemd[1]: Failed to start Network Service.

loqs

Member

Registered: 2014-03-06

Posts: 19,015

Re: systemd-networkd fails to start

status=200/CHDIR

Search engine results for the above are generally related to directory permissions.
What is the output of:

stat / /usr/lib/systemd/network /etc/systemd/network
SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-networkd