dhcpcd always times out on boot

yarmash · 2014-05-16 12:27:46

I have a really strange problem with dhcpcd on my Archlinux machine: dhcpcd always times out on boot, but if I (re)start it manually, it works fine. Here's the logs from journald:

-- Reboot --
May 16 14:56:56 epbyminw1076 systemd[1]: Starting dhcpcd on eno1...
May 16 14:56:57 epbyminw1076 dhcpcd[310]: version 6.3.2 starting
May 16 14:56:57 epbyminw1076 dhcpcd[310]: eno1: waiting for carrier
May 16 14:56:58 epbyminw1076 dhcpcd[310]: eno1: carrier acquired
May 16 14:56:59 epbyminw1076 dhcpcd[310]: DUID 00:01:00:01:19:92:10:5e:6c:3b:e5:33:0a:0a
May 16 14:56:59 epbyminw1076 dhcpcd[310]: eno1: IAID e5:33:0a:0a
May 16 14:56:59 epbyminw1076 dhcpcd[310]: eno1: rebinding lease of 10.6.44.58
May 16 14:57:04 epbyminw1076 dhcpcd[310]: eno1: DHCP lease expired
May 16 14:57:04 epbyminw1076 dhcpcd[310]: eno1: soliciting a DHCP lease
May 16 14:57:27 epbyminw1076 dhcpcd[310]: timed out
May 16 14:57:27 epbyminw1076 dhcpcd[310]: exited
May 16 14:57:27 epbyminw1076 systemd[1]: dhcpcd@eno1.service: control process exited, code=exited status=1
May 16 14:57:27 epbyminw1076 systemd[1]: Failed to start dhcpcd on eno1.
May 16 14:57:27 epbyminw1076 systemd[1]: Unit dhcpcd@eno1.service entered failed state.

# restart manually...

May 16 14:58:12 epbyminw1076 systemd[1]: Starting dhcpcd on eno1...
May 16 14:58:12 epbyminw1076 dhcpcd[906]: version 6.3.2 starting
May 16 14:58:12 epbyminw1076 dhcpcd[906]: DUID 00:01:00:01:19:92:10:5e:6c:3b:e5:33:0a:0a
May 16 14:58:12 epbyminw1076 dhcpcd[906]: eno1: IAID e5:33:0a:0a
May 16 14:58:13 epbyminw1076 dhcpcd[906]: eno1: soliciting a DHCP lease
May 16 14:58:24 epbyminw1076 dhcpcd[906]: eno1: offered 10.6.44.58 from 10.6.0.3
May 16 14:58:24 epbyminw1076 dhcpcd[906]: eno1: ignoring offer of 10.6.44.58 from 10.6.0.6
May 16 14:58:29 epbyminw1076 dhcpcd[906]: eno1: leased 10.6.44.58 for 259200 seconds
May 16 14:58:29 epbyminw1076 dhcpcd[906]: eno1: adding route to 10.6.0.0/18
May 16 14:58:29 epbyminw1076 dhcpcd[906]: eno1: adding default route via 10.6.0.1
May 16 14:58:29 epbyminw1076 dhcpcd[906]: forked to background, child pid 915
May 16 14:58:29 epbyminw1076 systemd[1]: Started dhcpcd on eno1.

My dhcpcd.conf:

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll
noipv6rs

# do not overwrite /etc/resolv.conf
nohook resolv.conf

I also tried rebooting with the stock /etc/dhcpcd.conf but it didn't change anything.
Any help is appreciated.

Trilby · 2014-05-16 13:46:33

I vaguely remember this coming up before, and it related to the ordering/timing of events with udev renaming the interfaces.

I'm not sure if adding a "Requires=" line with the same unit as the "After=" line would help. I know disabling the "predictable" interface names would do it if this is an option: you'd then worth with eth0 rather than eno1.

Head_on_a_Stick · 2014-05-16 13:48:18

You could try speeding up the dhcp client by disabling ARP probing...

Trilby · 2014-05-16 13:56:18

Speeding it up wont help - slowing it down would fix it, but that would be an odd fix.

It's timing out because udev hasn't yet renamed the interface from eth0 to eno1 when it tries to connect to eno1.

yarmash · 2014-05-16 16:15:10

If I enable dhcpcd like this: "systemctl enable dhcpcd", i.e. w/o using an interface name, it kind of works:

May 16 19:42:57 epbyminw1076 dhcpcd[315]: eno1: waiting for carrier
May 16 19:43:01 epbyminw1076 dhcpcd[315]: eno1: carrier acquired
May 16 19:43:01 epbyminw1076 dhcpcd[315]: DUID 00:01:00:01:19:92:10:5e:6c:3b:e5:33:0a:0a
May 16 19:43:01 epbyminw1076 dhcpcd[315]: eno1: IAID e5:33:0a:0a
May 16 19:43:01 epbyminw1076 dhcpcd[315]: eno1: soliciting a DHCP lease
May 16 19:48:18 epbyminw1076 dhcpcd[315]: eno1: offered 10.6.44.58 from 10.6.0.3
May 16 19:48:18 epbyminw1076 dhcpcd[315]: eno1: ignoring offer of 10.6.44.58 from 10.6.0.6
May 16 19:48:22 epbyminw1076 dhcpcd[315]: eno1: leased 10.6.44.58 for 259200 seconds
May 16 19:48:22 epbyminw1076 dhcpcd[315]: eno1: adding route to 10.6.0.0/18
May 16 19:48:22 epbyminw1076 dhcpcd[315]: eno1: adding default route via 10.6.0.1

But it takes several minutes to obtain an IP-address.

Last edited by yarmash (2014-05-16 17:12:51)

Arch Linux

#1 2014-05-16 12:27:46

dhcpcd always times out on boot

#2 2014-05-16 13:46:33

Re: dhcpcd always times out on boot

#3 2014-05-16 13:48:18

Re: dhcpcd always times out on boot

#4 2014-05-16 13:56:18

Re: dhcpcd always times out on boot

#5 2014-05-16 16:15:10

Re: dhcpcd always times out on boot

Board footer