How to revert to ISC DHCP server? Immediately
-
Switched to Kea. It stopped and won't restart. Dead in the water without working DHCP server!
-
@rloeb Kea continuously fails:
ERROR [kea-dhcp4.dhcp4.0x1c6fe2c12000] 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 -
Hi- As far as I understand you just need to select ISC as the server backend and then save.
-
@Uglybrian But I can't remember how to do that. A bit stressed out fighting with the 23.09 update.
-
@rloeb Figured it out... System|Advanced|Networking.
-
Go to system, then on the drop down select advanced, from advanced select networking. You will see it at the top under DHCH options.
-
@rloeb said in How to revert to ISC DHCP server? Immediately:
ERROR [kea-dhcp4.dhcp4.0x1c6fe2c12000] 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
KEA service stopping through the day
I've saw this error ones, and i guess it happened when I was saving settings on the unbound settings page. This while restart the dhcp server(s) : dhcpd or kea, if that's the one being used.
The error log message is self explainable : ditch the indicated "/tmp/kea4-ctrl-socket.lock" file - a zero byte file so no big loss ^^ and kea will restart without issues.
I've kept kea running since, and looking out for further events, but haven't seen anything.
It's probability the good old "If I don't mess around with my pfSense, clicking on all kind of buttons all the time" situation : I touching nothing so it's rock solid.kea is - my words - bleeding edge technology (not kea, but the implementation in a pure GUI environment), so it's quiet normal that you see some ... blood ? That's why you can opt-in and opt-out.
But it needs to be tested 'in the wild' to get a max of feedback. Like you did
-
@Gertjan Thank you!
I reverted to ISC to keep my company operating. Based on the disruption caused by the 23.09 upgrade, it will be a very long time before we make any modifications to pfsense! -
@rloeb Same here. It works for some minutes after reboot, and then stops forever. Kea is clearly unstable, I will switch back to ISC.
Nov 30 18:22:00 kea-dhcp6 22872 ERROR [kea-dhcp6.dhcp6.0x1f3e45812000] DHCP6_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp6.conf': cannot lock socket lockfile, /tmp/kea6-ctrl-socket.lock, : Resource temporarily unavailable
Nov 30 18:22:00 kea-dhcp6 22872 ERROR [kea-dhcp6.dhcp6.0x1f3e45812000] DHCP6_CONFIG_LOAD_FAIL configuration error using file: /usr/local/etc/kea/kea-dhcp6.conf, reason: cannot lock socket lockfile, /tmp/kea6-ctrl-socket.lock, : Resource temporarily unavailable
Nov 30 18:22:00 kea-dhcp6 22872 ERROR [kea-dhcp6.dhcp6.0x1f3e45812000] DHCP6_PARSER_COMMIT_FAIL parser failed to commit changes: cannot lock socket lockfile, /tmp/kea6-ctrl-socket.lock, : Resource temporarily unavailable -
(Already made a separate thread, when I saw this thread, just to be complete adding my crash here also)
With 2.7.1. release I have switched to KEA DHCP and today it it crashed. The only thing I can trace back (logs have 500 max entries) that service watchdog detected service kea-dhcp4 stopped. Restarting kea-dhcp4 (KEAS DHCP server) and this is repeated so many times that it clogged the logs, until I did a reboot of pfSense.