Stale Kea control socket lock file can prevent Kea from starting
If for some reason the Kea control socket lock file is present while Kea is stopped, then Kea can never start until that file is removed.
Attempting to start Kea while
/tmp/kea4-ctrl-socket.lock exists, even if Kea is not currently running, results in a fatal error preventing Kea from running:
Nov 13 13:07:53 kea-dhcp4 32826 ERROR [kea-dhcp4.dhcp4.0x1c655d812000] DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp4.conf': cannot lock socket lockfile, /tmp/kea4-ctrl-socket.lock, : Resource temporarily unavailable
Removing the socket file allows Kea to start (
Forum thread: https://forum.netgate.com/post/1135910
No data to display