Bug #14977
closed
Stale Kea control socket lock file can prevent Kea from starting
100%
Description
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 (rm /tmp/kea4-ctrl-socket.lock).
Forum thread: https://forum.netgate.com/post/1135910
Updated by Suriname Clubcard about 1 month ago
I just experienced exactly this same problem:
DHCP4_CONFIG_LOAD_FAIL configuration error using file: /usr/local/etc/kea/kea-dhcp4.conf, reason: cannot lock socket lockfile, /tmp/kea4-ctrl-socket.lock, : Resource temporarily unavailable
pfSense 2.7.2.
Updated by Jim Pingle about 1 month ago
- Status changed from New to Closed
- % Done changed from 0 to 100
I can't reproduce this at all on current snapshots. I've killed the process and left the old file in place, killed it and made a file owned by another user, killed it and made a file with invalid permissions, and so on. Every time it starts right back up perfectly. I've tried restarting the process by save/apply, by using the service controls, and so on. I even killed it, left the lock in place, and rebooted. Every time it starts right up.
It's possible they fixed it upstream or something else changed that made it a non-issue.