KEA DHCP not serving IP-Addresses

[NetRunner8050]

Hey Guys,

Its me again.

After switching my Uplink to my Switch KEA Service is not serving any IP-Adresses.
The Service is running but no device gets any IP-Address.

For a work around I changed the DHCP to ISC DHCP and it work immediately.

Where could I start with the trouble shooting?

In the logs under Status/System Logs/DHCP I dont see anything.

What I got were that the service crashed with the Error:
ERROR [kea-dhcp4.dhcp4.0x245d9f412000] 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

But after deleting the file /tmp/kea4-ctrl-socket.lock manually it solved the issue and the service started again.

Has somebody a hint where to start troubleshooting?

[bmeeks]

@NetRunner8050 said in KEA DHCP not serving IP-Addresses:

Hey Guys,

Its me again.

After switching my Uplink to my Switch KEA Service is not serving any IP-Adresses.
The Service is running but no device gets any IP-Address.

For a work around I changed the DHCP to ISC DHCP and it work immediately.

Where could I start with the trouble shooting?

In the logs under Status/System Logs/DHCP I dont see anything.

What I got were that the service crashed with the Error:
ERROR [kea-dhcp4.dhcp4.0x245d9f412000] 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

But after deleting the file /tmp/kea4-ctrl-socket.lock manually it solved the issue and the service started again.

Has somebody a hint where to start troubleshooting?

Usually when an application crashes unexpectedly, it will leave orphaned PID and socket files hanging around that impede the next startup attempt. Removing those orphaned files will usually solve the startup issue.

However, you would still want to examine the system logs carefully to see if any reason can be found for the crash that resulted in the orphaned files.

Kea is not yet ready to fully replace ISC DCHP. There are many limitations with the current package in pfSense today. My suggestion is to stay with ISC DHCP until Kea is more fully fleshed out and more of its options work. There are several posts around the Forum about the existing limitations of Kea.

[SteveITS]

@NetRunner8050 said in KEA DHCP not serving IP-Addresses:

cannot lock socket lockfile

https://redmine.pfsense.org/issues/14977

I also suggest staying with ISC DHCP unless you are actively testing something in Kea. There are several limitations:

https://docs.netgate.com/pfsense/en/latest/releases/23-09.html#kea-dhcp-server-feature-preview-now-available