Too bad I don’t know. In the past I thought it has something to do with the hypervisor and it’s time to do some software maintenance, because it happened just once for a couple of weeks. However that was not the cause. Killing and restarting the dhcpcd or rebooting ipfire fixes that issue.
Could you go back and install the appropriate CU and test to see which version your problem started with?
CU200 Testing released with 10.3.0 and reverted back to 10.2.4
CU196 released with 10.2.4
CU193 released with 10.2.2
CU190 released with 10.1.0
CU189 released with 10.0.10
So 10.2.4 still showed the problem for you
so the next version back would be CU193 with 10.2.2
then CU190 with 10.1.0
and then CU189 with 10.0.10 which would be a year and a half ago so these CU’s should cover the problem.
I can go back the log to the 17th july 2025 and I have that error message from the first day on.
I have just checked back on my system to start of July 2025 and I have never seen those messages in my dhcpcd logs.
Going back that far in time it is clearly not related to the CU200 Testing update.
A pid failing to exit suggests a problem trying to terminate the process.
What permissions and ownerships do you have in the /var/run/dhcpcd/ directory.
Here is mine
ls -hal /var/run/dhcpcd/
total 4.0K
drwxr-xr-x 3 root root 120 Mar 2 17:52 .
drwxr-xr-x 19 root root 1.2K Mar 2 22:05 ..
drwxr-x--- 2 dhcpcd dhcpcd 40 Mar 2 17:52 chroot
srw-rw---- 1 root root 0 Mar 2 17:52 red0-4.sock
srw-rw-rw- 1 root root 0 Mar 2 17:52 red0-4.unpriv.sock
-rw-r--r-- 1 root root 5 Mar 2 17:52 red0.pid
No. Red is connected via an rj45 nic connection.
If you are using wlan for the red connection, then I can’t help as I have never used that and have no hardware to be able to evaluate it.
So why do you compare your situation with users who use wlan clients on RED?
This error only occurs when a connection is lost (lost carrier signal). You usually don’t have that via wired connection.
Because I didn’t know you were using wireless client on your red connection.
You can still get a carrier lost, carrier acquired or a waiting for carrier message with dhcpcd and a wired connection.
EDIT:
What do you get in the System Logs for the Wireless entry. Maybe there is some clue in those logs for what is causing dhcpcd a problem.
1 Like
I know you always try to help and you are a very active and valuable person here, of course I don’t want to be rude: this has been told a few times, also with the bug report of dhcpcd. However I watched the issue section on git today and there are a few serious problems with it. Also our problem with 10.3.0 is well known.
In my opinion there is nothing we can do about it. 
Empty, because it’s about wlan hosts.
This could be tested by installing old core updates and watch the kernel log. But do we benifit from this tests?