Kea DHCP stops working
-
@maverickws
The same here ,,, But I found the solution:
login with an sftp clientdirectory /root/tmp chmod 777 (allow all)
delete /root/tmp/kea4-ctrl-socket
delete /root/tmp/kea4-ctrl-socket.lock
restart Kea DHCP server (the sockets are automaticaly created)
done!
however this issue may hapen again after some days ... -
@noisyjohn Hi there and thank you for your input.
However, I have been forced out of KEA.
The reasons are described in this topic:
Ater Kea for 1 year, reverted back to ISC -
I believe we now have a fix for this. Keep an eye out for a public beta of 24.11 very soon.
-
@cmcdonald Is there any intent to release this in the Community Edition? It's now been over a year since the last major version release, and the issues are stacking up. It's starting to feel like the project is stagnating.
-
@zkhcohen said in Kea DHCP stops working:
and the issues are stacking up ...
This thread, this issue, only exists in 24.03.
It concerns KEA, the 'new' DHCP server/client that is going to replace ISC DHCP in the future. The latter is used in 2.7.2 and is working very well - I'm using it also in 24.03.Right now, no one really wants 'new versions' as most of us try to deal with 24H2 and its 'new things' that no one was asking for, but we still got (to debug) it ...
-
@Gertjan I can personally confirm that this issue is present in CE 2.7.2 with the same symptoms.
I'm not sure how you can claim that no one "wants a new version" when there are numerous threads off and on this forum asking for exactly that.
-
@zkhcohen said in Kea DHCP stops working:
issue is present in CE 2.7.2 with the same symptoms.
Aha, so 2.7.2 has also the KEA !? I stand corrected.
I really had the impression that only pfSense Plus (24.03) had this test-drive KEA addition.Easy way out then : keep the 30+ years tested an proved "DHCP ISC" and the issue will be gone.
-
I see this is still ongoing. I found a workaround via watchdog service. The script does a cleanup before attempting to restart the sevice
-
list itemmake sure you install the watchdog service in pfsense.
-
list Add the kea dhcp 4 service.
-
Shell into pfsense and change to /usr/local/etc/rc.d
-
list Create a backup of kea service script. cp kea kea.old
-
list edit the kea file and replace contents with script below
#!/bin/sh # PROVIDE: kea # REQUIRE: NETWORK netif routing # KEYWORD: shutdown . /etc/rc.subr name=kea desc="Kea DHCP Server" rcvar=kea_enable load_rc_config $name kea_enable=${kea_enable:-"NO"} command="/usr/local/sbin/keactrl" required_files="/usr/local/etc/${name}/keactrl.conf" # Add cleanup function cleanup_kea() { # Clean up stale lock files rm -f /tmp/kea4-ctrl-socket.lock # Kill any zombie processes pkill -9 kea-dhcp4 # Wait for processes to die sleep 2 } # Modify start command to include cleanup start_cmd() { cleanup_kea ${command} start logger -t kea-watchdog "Kea DHCP4 started with cleanup" } # Modify stop command to include cleanup stop_cmd() { ${command} stop cleanup_kea logger -t kea-watchdog "Kea DHCP4 stopped with cleanup" } status_cmd="$command status" reload_cmd="$command reload" extra_commands="reload" run_rc_command "$1"
Watchdog should auto restart the service
-
-
@datpif Actually just found watchdog starts a different service . so the simplest fix i found was to edit
-
/etc/inc/service-utils.inc
-
search for case 'kea-dhcp4':
-
and add
case 'kea-dhcp4': exec("rm -f /tmp/kea4-ctrl-socket.lock");
-
-
@datpif yeap! clever. I knew this problem /tmp/kea4-ctrl-socket.lock"". But this automation is grate. Thanks for this. But it is still a work around, not a fix. I wander if anyone in KEA will take care of this.
However I'm gona say goodby to KEA. The reason:
KEA does not register the DHCP clients in dns resolver, so my local net (5 pcs) never works as I want. I have read somewhere that it' does it automaticaly, but it does not. And there is no option "register dhcp clients" as the older ISC DHCP does. -
It does in 24.11.