You are not logged in.

#1 2018-08-13 06:32:35

7thSon
Member
Registered: 2017-05-07
Posts: 132

Networking not starting up properly on boot

Seems like my networking has been failing the last few weeks on boot, I realized that its been necessary for me to go into a terminal and running "dhcpcd enp5s0" on every boot lately to get networking to kick into gear.
I can also see that I get a message in the boot terminal saying "Failed to start dhcpcd on enp5s0", but this works just fine when I do it in a terminal once I've booted into arch and XFCE.
The systemd service for dhcpcd is enabled and started as well, so no issue there it seems.

Has there been any recent changes to networking in Arch (I haven't really changed anything in my network settings, so it seems to me this might be some update that broke something).
Is there anything I can do to check this except add "dhcpcd en5s0" to my startup commands?  (don't really want to do this)

Offline

#2 2018-08-13 06:38:48

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 25,537
Website

Re: Networking not starting up properly on boot

Read your journal and see why the service is failing.


Moving to NC...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Online

#3 2018-08-13 18:10:43

7thSon
Member
Registered: 2017-05-07
Posts: 132

Re: Networking not starting up properly on boot

jasonwryan wrote:

Read your journal and see why the service is failing.


Moving to NC...

I found this in my journal:

Aug 13 08:28:54 arch systemd[1]: Starting dhcpcd on all interfaces...
Aug 13 08:28:54 arch systemd[1]: Starting dhcpcd on enp5s0...
Aug 13 08:28:54 arch dhcpcd[584]: sending commands to master dhcpcd process
Aug 13 08:28:54 arch systemd[1]: dhcpcd@enp5s0.service: Can't open PID file /run/dhcpcd-enp5s0.pid (yet?) after start: No such file or directory
Aug 13 08:28:54 arch systemd[1]: dhcpcd@enp5s0.service: Failed with result 'protocol'.
Aug 13 08:28:54 arch systemd[1]: Failed to start dhcpcd on enp5s0.
Aug 13 08:28:55 arch dhcpcd[577]: dev: loaded udev
Aug 13 08:28:55 arch dhcpcd[577]: forked to background, child pid 617
Aug 13 08:28:55 arch systemd[1]: Started dhcpcd on all interfaces.
Aug 13 08:28:56 arch dhcpcd[617]: enp5s0: waiting for carrier
Aug 13 08:28:56 arch dhcpcd[617]: control command: /usr/bin/dhcpcd -q -w enp5s0
Aug 13 08:28:58 arch dhcpcd[617]: docker0: waiting for carrier
Aug 13 08:28:59 arch dhcpcd[617]: enp5s0: carrier acquired
Aug 13 08:28:59 arch dhcpcd[617]: DUID 00:01:00:01:22:21:ba:70:bc:5f:f4:49:69:23
Aug 13 08:28:59 arch dhcpcd[617]: enp5s0: IAID f4:49:69:23
Aug 13 08:28:59 arch dhcpcd[617]: enp5s0: adding address fe80::ef32:15a8:c121:c76d
Aug 13 08:28:59 arch dhcpcd[617]: enp5s0: soliciting an IPv6 router
Aug 13 08:29:00 arch dhcpcd[617]: enp5s0: rebinding lease of 192.168.1.110
Aug 13 08:29:00 arch dhcpcd[617]: enp5s0: probing address 192.168.1.110/24
Aug 13 08:29:05 arch dhcpcd[617]: enp5s0: leased 192.168.1.110 for 86400 seconds
Aug 13 08:29:05 arch dhcpcd[617]: enp5s0: adding route to 192.168.1.0/24
Aug 13 08:29:05 arch dhcpcd[617]: enp5s0: adding default route via 192.168.1.1
Aug 13 08:29:12 arch dhcpcd[617]: enp5s0: no IPv6 Routers available

Seems like the service fails to open the PID file. Should I try deleting it if it exists, or would there be some other reason why this problem has popped up all of a sudden?
The later part of the journal is from me running "dhcpcd enp5s0" manually in a terminal.

Offline

Board footer

Powered by FluxBB