Arch Linux

chrisd

Member

Registered: 2020-09-06

Posts: 9

dhcpcd no longer works after upgrade, works after downgrading

Dear all,

This evening I updated my archlinux32 laptop. After the upgrade networking was no longer
working. I found out that the problem was that dhcpcd was no longer starting correctly.
Journalctl output of attempting to start it is

Nov 24 20:53:47 lappie systemd[1]: Starting dhcpcd on all interfaces...
Nov 24 20:53:47 lappie dhcpcd[899]: main: control_open: Connection refused
Nov 24 20:53:47 lappie dhcpcd[899]: main: control_open: Connection refused
Nov 24 20:53:47 lappie dhcpcd[899]: dhcpcd-9.3.2 starting
Nov 24 20:53:47 lappie dhcpcd[902]: dev: loaded udev
Nov 24 20:53:47 lappie dhcpcd[902]: DUID 00:01:00:01:22:3a:e3:d2:00:1b:24:40:cb>
Nov 24 20:53:47 lappie dhcpcd[902]: ps_ctl_listen: read: Success
Nov 24 20:53:47 lappie dhcpcd[899]: ps_ctl_listen: read: Success
Nov 24 20:55:17 lappie systemd[1]: dhcpcd.service: start operation timed out. T>
Nov 24 20:55:17 lappie dhcpcd[899]: dhcpcd_signal_cb: write: Connection refused
Nov 24 20:56:47 lappie systemd[1]: dhcpcd.service: State 'stop-sigterm' timed o>
Nov 24 20:56:47 lappie systemd[1]: dhcpcd.service: Killing process 899 (dhcpcd)>
Nov 24 20:56:47 lappie systemd[1]: dhcpcd.service: Killing process 902 (dhcpcd)>
Nov 24 20:56:47 lappie systemd[1]: dhcpcd.service: Killing process 903 (dhcpcd)>
Nov 24 20:56:47 lappie systemd[1]: dhcpcd.service: Control process exited, code>
Nov 24 20:56:47 lappie systemd[1]: dhcpcd.service: Failed with result 'timeout'.
Nov 24 20:56:47 lappie systemd[1]: Failed to start dhcpcd on all interfaces.

I solved this problem by downgrading from dhcpcd version 9.3.2-1.0 back to 9.2.0-1.0.
After doing that and doing 'systemctl restart dhcpcd' it works again and I can, e.g.,
surf the web again. Might there be something wrong with the current version of
dhcpcd?

All the best,
Chris

levi

Moderator

From: Yorkshire, UK

Registered: 2018-06-16

Posts: 1,197

Re: dhcpcd no longer works after upgrade, works after downgrading

Yeah, dhcpd has been having troubles recently; see this announcement about it.  And here's my experience of it breaking for my uses.

In short, you can either configure a static ip and therefore stop depending on dhcpd, or switch to using dhclient instead of dhcpd.  I went for the latter approach in the end.

I'm not sure your experiencing the same happening as I did.  I don't seem to have investigated my journalctl log, but dhcpd timing out may well have happened.  I just observed my network not coming up and copied what seemed to be working for my on my other boxen.

---

Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.