> My problem was that I had two services using same RuntimeDirectory (isc-dhcp-server and isc-dhcp-server6), but I configured only one to work. So when the second one died, its runtime directory got removed, making it a problem for the first service.
Since I have only the IPv4 addresses configured as well, I decided to look into this.
When I tested this out by changing the RuntimeDirectory to "dhcp-server6" and the exec line's PID file parameter to "-pf /run/dhcp-server6/dhcpd6.pid", everything worked as it should on a reboot. The PID file was created for /run/dhcp-server/dhcpd.pid successfully.
So I found a comment at https:/ /unix.stackexch ange.com/ a/533900/ 253840
> My problem was that I had two services using same RuntimeDirectory (isc-dhcp-server and isc-dhcp-server6), but I configured only one to work. So when the second one died, its runtime directory got removed, making it a problem for the first service.
Since I have only the IPv4 addresses configured as well, I decided to look into this.
When I tested this out by changing the RuntimeDirectory to "dhcp-server6" and the exec line's PID file parameter to "-pf /run/dhcp- server6/ dhcpd6. pid", everything worked as it should on a reboot. The PID file was created for /run/dhcp- server/ dhcpd.pid successfully.