[SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

BonnieTwin · 2020-04-20 12:58:16

Carried out pacman -Syu update today and after rebooting no IP address is being obtained from my dhcp server.
dhcpcd version before upgrade was 8.1.7-1 and after 9.0.1-2.

Downgrading back to 8.1.7-1 and rebooting makes everything work again. Have swapped between the two versions twice and each time 9.0.1 won't get an IP address and 8.1.7 works fine.

Here is the status output for 9.0.1

 systemctl status dhcpcd@enp1s0.service

● dhcpcd@enp1s0.service - dhcpcd on enp1s0
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled; vendor preset: disabled)
     Active: failed (Result: protocol) since Mon 2020-04-20 13:17:05 CEST; 18min ago
    Process: 1533 ExecStart=/usr/bin/dhcpcd -q -w enp1s0 (code=exited, status=0/SUCCESS)

Apr 20 13:17:05 hyperion dhcpcd[1543]: enp1s0: IAID 61:a0:f1:bf
Apr 20 13:17:05 hyperion dhcpcd[1543]: ipv6_addaddr1: Operation not supported
Apr 20 13:17:05 hyperion dhcpcd[1543]: ps_dostop: Connection refused
Apr 20 13:17:05 hyperion dhcpcd[1543]: enp1s0: adding address fe80::5e49:8f02:434a:330c
Apr 20 13:17:05 hyperion dhcpcd[1543]: ipv6_addaddr1: Operation not supported
Apr 20 13:17:05 hyperion dhcpcd[1543]: ps_dostop: Connection refused
Apr 20 13:17:05 hyperion dhcpcd[1543]: dhcpcd exited
Apr 20 13:17:05 hyperion systemd[1]: dhcpcd@enp1s0.service: Can't open PID file /run/dhcpcd/enp1s0.pid (yet?) after start: Operation not permitted
Apr 20 13:17:05 hyperion systemd[1]: dhcpcd@enp1s0.service: Failed with result 'protocol'.
Apr 20 13:17:05 hyperion systemd[1]: Failed to start dhcpcd on enp1s0.

and the journalctl output

 journalctl -xe | grep dhcpcd

Apr 20 14:21:59 hyperion systemd[1]: Created slice system-dhcpcd.slice.
Apr 20 14:22:04 hyperion systemd[1]: Starting dhcpcd on enp1s0...
-- Subject: A start job for unit dhcpcd@enp1s0.service has begun execution
-- A start job for unit dhcpcd@enp1s0.service has begun execution.
Apr 20 14:22:04 hyperion dhcpcd[527]: dhcpcd-9.0.1 starting
Apr 20 14:22:04 hyperion dhcpcd[555]: ps_inet_startcb: ipv6nd_open: Address family not supported by protocol
Apr 20 14:22:04 hyperion dhcpcd[555]: ps_start: Address family not supported by protocol
Apr 20 14:22:04 hyperion dhcpcd[555]: ps_inet_startcb: ipv6nd_open: Address family not supported by protocol
Apr 20 14:22:04 hyperion dhcpcd[555]: ps_start: Address family not supported by protocol
Apr 20 14:22:04 hyperion dhcpcd[553]: enp1s0: waiting for carrier
Apr 20 14:22:04 hyperion dhcpcd[553]: ps_dostop: Connection refused
Apr 20 14:22:04 hyperion dhcpcd[553]: ps_dostop: Connection refused
Apr 20 14:22:04 hyperion dhcpcd[553]: dhcpcd exited
Apr 20 14:22:04 hyperion systemd[1]: dhcpcd@enp1s0.service: Can't open PID file /run/dhcpcd/enp1s0.pid (yet?) after start: Operation not permitted
Apr 20 14:22:04 hyperion systemd[1]: dhcpcd@enp1s0.service: Failed with result 'protocol'.
-- The unit dhcpcd@enp1s0.service has entered the 'failed' state with result 'protocol'.
Apr 20 14:22:04 hyperion systemd[1]: Failed to start dhcpcd on enp1s0.
-- Subject: A start job for unit dhcpcd@enp1s0.service has failed
-- A start job for unit dhcpcd@enp1s0.service has finished with a failure.
Apr 20 14:22:04 hyperion audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp1s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

I want to check if anyone has any ideas of obvious things to fix this before I consider reporting a bug.

Last edited by BonnieTwin (2020-04-20 17:14:44)

Trilby · 2020-04-20 13:05:30

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

BonnieTwin · 2020-04-20 13:21:50

I saw that post but the problem there was that both dhcpcd and Network Manager were installed and being used at the same time. I am only using dhcpcd. Network Manager is not installed on my system.

Also that poster was receiving an IP address but having problems with name resolution. I don't receive any IP address.

Sorry if I am being obtuse but is there something I am missing from that post?

seth · 2020-04-20 13:37:02

Does the global, NIC agnostic service still start?

BonnieTwin · 2020-04-20 13:58:09

If I am understanding correctly you want to know what happens if I try and start the dhcpcd.service file.

Here are the status and journalctl outputs from doing that. It doesn't start.

systemctl start dhcpcd.service
systemctl status dhcpcd.service

● dhcpcd.service - dhcpcd on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2020-04-20 15:45:23 CEST; 2min 5s ago
    Process: 844 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
    Process: 860 ExecStop=/usr/bin/dhcpcd -x (code=exited, status=1/FAILURE)
   Main PID: 854 (code=exited, status=0/SUCCESS)

Apr 20 15:45:23 hyperion dhcpcd[854]: DUID 00:01:00:01:26:30:38:34:00:d8:61:a0:f1:bf
Apr 20 15:45:23 hyperion dhcpcd[854]: enp1s0: IAID 61:a0:f1:bf
Apr 20 15:45:23 hyperion dhcpcd[854]: enp1s0: adding address fe80::5e49:8f02:434a:330c
Apr 20 15:45:23 hyperion dhcpcd[854]: ipv6_addaddr1: Operation not supported
Apr 20 15:45:23 hyperion dhcpcd[854]: ps_dostop: Connection refused
Apr 20 15:45:23 hyperion dhcpcd[854]: dhcpcd exited
Apr 20 15:45:23 hyperion dhcpcd[860]: dhcpcd not running
Apr 20 15:45:23 hyperion dhcpcd[860]: dhcpcd not running
Apr 20 15:45:23 hyperion systemd[1]: dhcpcd.service: Control process exited, code=exited, status=1/FAILURE
Apr 20 15:45:23 hyperion systemd[1]: dhcpcd.service: Failed with result 'exit-code'.


journalctl -xe | grep dhcpcd

Apr 20 15:45:23 hyperion systemd[1]: Starting dhcpcd on all interfaces...
-- Subject: A start job for unit dhcpcd.service has begun execution
-- A start job for unit dhcpcd.service has begun execution.
Apr 20 15:45:23 hyperion dhcpcd[844]: dhcpcd-9.0.1 starting
Apr 20 15:45:23 hyperion dhcpcd[856]: ps_inet_startcb: ipv6nd_open: Address family not supported by protocol
Apr 20 15:45:23 hyperion dhcpcd[856]: ps_start: Address family not supported by protocol
Apr 20 15:45:23 hyperion dhcpcd[856]: ps_inet_startcb: ipv6nd_open: Address family not supported by protocol
Apr 20 15:45:23 hyperion dhcpcd[856]: ps_start: Address family not supported by protocol
Apr 20 15:45:23 hyperion dhcpcd[854]: dev: loaded udev
Apr 20 15:45:23 hyperion systemd[1]: Started dhcpcd on all interfaces.
-- Subject: A start job for unit dhcpcd.service has finished successfully
-- A start job for unit dhcpcd.service has finished successfully.
Apr 20 15:45:23 hyperion audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 20 15:45:23 hyperion kernel: audit: type=1130 audit(1587390323.414:83): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 20 15:45:23 hyperion dhcpcd[854]: DUID 00:01:00:01:26:30:38:34:00:d8:61:a0:f1:bf
Apr 20 15:45:23 hyperion dhcpcd[854]: enp1s0: IAID 61:a0:f1:bf
Apr 20 15:45:23 hyperion dhcpcd[854]: enp1s0: adding address fe80::5e49:8f02:434a:330c
Apr 20 15:45:23 hyperion dhcpcd[854]: ipv6_addaddr1: Operation not supported
Apr 20 15:45:23 hyperion dhcpcd[854]: ps_dostop: Connection refused
Apr 20 15:45:23 hyperion dhcpcd[854]: dhcpcd exited
Apr 20 15:45:23 hyperion dhcpcd[860]: dhcpcd not running
Apr 20 15:45:23 hyperion dhcpcd[860]: dhcpcd not running
Apr 20 15:45:23 hyperion systemd[1]: dhcpcd.service: Control process exited, code=exited, status=1/FAILURE
-- An ExecStop= process belonging to unit dhcpcd.service has exited.
Apr 20 15:45:23 hyperion systemd[1]: dhcpcd.service: Failed with result 'exit-code'.
-- The unit dhcpcd.service has entered the 'failed' state with result 'exit-code'.
Apr 20 15:45:23 hyperion audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Last edited by BonnieTwin (2020-04-20 13:59:10)

Trilby · 2020-04-20 13:58:27

Network manager was not relevant to the other thread. The second user who chimed in with an unrelated issue was using networkmanager.

seth · 2020-04-20 14:20:42

Can you "sudo dhcpcd -4"?
(error message + dhcpcd git just sew a bunch of commits looking very related)

BonnieTwin · 2020-04-20 15:27:38

I did "sudo dhcpcd -4" with 9.0.1 and got an IP address.

sudo dhcpcd -4

dhcpcd-9.0.1 starting
dev: loaded udev
DUID 00:01:00:01:26:30:38:34:00:d8:61:a0:f1:bf
enp1s0: IAID 61:a0:f1:bf
enp1s0: rebinding lease of 192.168.26.32
enp1s0: probing address 192.168.26.32/24
enp1s0: leased 192.168.26.32 for 3600 seconds
enp1s0: adding route to 192.168.26.0/24
enp1s0: adding default route via 192.168.26.254
forked to background, child pid 1349



ip addr (before running command)

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:d8:61:a0:f1:bf brd ff:ff:ff:ff:ff:ff

ip addr (after running command)

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:d8:61:a0:f1:bf brd ff:ff:ff:ff:ff:ff
    inet 192.168.26.32/24 brd 192.168.26.255 scope global dynamic noprefixroute enp1s0
       valid_lft 3572sec preferred_lft 3122sec

The IP address then enables me to access my network and the Internet. How do I get the system to do this during booting with the systemd dhcpcd services.

loqs · 2020-04-20 16:12:28

Does dhcpcd 9.0.1-4 currently in testing resolve the issue?

BonnieTwin · 2020-04-20 17:10:34

version 9.0.1-4 solved the problem. Thanks very much.

seth · 2020-04-20 19:29:17

How do I get the system to do this during booting with the systemd dhcpcd services.

Ftr, https://wiki.archlinux.org/index.php/Sy … ided_units

Arch Linux

#1 2020-04-20 12:58:16

[SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#2 2020-04-20 13:05:30

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#3 2020-04-20 13:21:50

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#4 2020-04-20 13:37:02

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#5 2020-04-20 13:58:09

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#6 2020-04-20 13:58:27

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#7 2020-04-20 14:20:42

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#8 2020-04-20 15:27:38

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#9 2020-04-20 16:12:28

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#10 2020-04-20 17:10:34

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

#11 2020-04-20 19:29:17

Re: [SOLVED] service not starting after dhcpcd upgrade 8.1.7-1 to 9.0.1-2

Board footer