Project

General

Profile

Actions

Bug #14977

open

Kea fails to restart due to race between process termination and startup

Added by Jim Pingle about 1 year ago. Updated 22 days ago.

Status:
Feedback
Priority:
Normal
Category:
DHCP (IPv4)
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
Affected Architecture:

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


Related issues

Has duplicate Regression #15823: Kea service is down and cannot be enabled after down eventDuplicateChristian McDonald

Actions
Actions

Also available in: Atom PDF