Dear Colleagues,

I have faced this issue as well, and managed to find the root cause of this 
issue.

It seems that the culprit is caused by the systemd unit file, as systemd itself 
can not found the configured pid file and eventually kills dhcpcd.
dhcpcd works just fine if you are starting it in foreground mode.

To check where dhcpcd put its pidfile, run 'dhcpcd -P' in the cli. 
On my system it prints this: '/run/dhcpcd/pid'

After changing the PIDFile stanza in the unit file from '/run/dhcpcd.pid' to 
'/run/dhcpcd/pid' and do the necessary 'systemctl daemon-reload' dance, dhcpcd 
starts just fine.

Some troubling logs are still there, like: 

ps_dropprivs: chroot: /usr/lib/dhcpcd: Operation not permitted

which might need further actions, but the basic functionality has been restored 
with this small change.

Regards,
János Pásztor

Reply via email to