dhcpcd-discuss

Hi Jouke

Sorry for the late reply.

On 08/08/2020 17:27, Jouke Witteveen wrote:
> I've been receiving some bugreports from netctl users that use the combination:
> netctl + ifplugd + dhcpcd
> The role of netctl is rather minimal. It provides a service file and a
> script for ifplugd. The issues started with dhcpcd 9, so I think the
> bug might be related to dhcpcd. One user once managed to get very
> similar issues with using just dhpcd.
>
> When suspending to RAM and resuming, dhcpcd reports a pipe error. The
> following journal segment is taken from the netctl bug report
> (https://bugs.archlinux.org/task/67382):
>
> ago 07 12:20:10 stryke dhcpcd[2221]: sending signal TERM to pid 1312
> ago 07 12:20:10 stryke dhcpcd[2221]: waiting for pid 1312 to exit
> ago 07 12:20:10 stryke dhcpcd[1312]: script_runreason: Resource
> temporarily unavailable
> ago 07 12:20:10 stryke dhcpcd[1312]: eth0: deleting address
> fe80::145e:4e49:22aa:5f8d
> ago 07 12:20:10 stryke dhcpcd[1312]: ipv6_deleteaddr: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: arp_free: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: eth0: ipv4_deladdr: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: eth0: deleting route to 192.168.1.0/24
> ago 07 12:20:10 stryke dhcpcd[1312]: rt_delete: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: eth0: deleting default route via
> 192.168.1.254
> ago 07 12:20:10 stryke dhcpcd[1312]: rt_delete: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: script_runreason: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: main: control_stop: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: ps_dostop: Broken pipe
> ago 07 12:20:10 stryke dhcpcd[1312]: dhcpcd exited
> ago 07 12:20:10 stryke dhcpcd[1313]: ps_root_recvmsg: Connection refused
> ago 07 12:20:10 stryke dhcpcd[1313]: ps_root_recvmsg: Connection refused
>
> If this is a known problem, I would like to know what netctl can do to
> prevent it.

So, the actual bug report is that dhcpcd is "inactive".
The errors reported are just errors (which I should try and fix if I can 
reproduce it on a Linux VM - how do I suspend and resume that?).

All I can say for sure is that something is stopping dhcpcd - ie `dhcpcd -x` was 
called.
> ago 07 12:20:10 stryke dhcpcd[2221]: sending signal TERM to pid 1312
> ago 07 12:20:10 stryke dhcpcd[2221]: waiting for pid 1312 to exit
> ago 07 12:20:10 stryke dhcpcd[1312]: dhcpcd exited

But I see nothing re-starting it.
dhcpcd cannot be expected to start itself - and that is the real issue yes?

So beyond fixing the broken pipe errors I don't see anything else I can help with.

Roy