Kea server is down
-
Hello all
I found my KEa DHCP server down today and after checking logs see:
Oct 14 12:05:42 kea-dhcp4 80653 ERROR [kea-dhcp4.dhcp4.0x16822f212000] 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
Any clues on how to fix it?
TIA
-
@chudak We have had a very hard time reproducing this problem internally. However, I believe I can at least mitigate it without knowing the exact root cause. Will get this into 24.11.
-
I believe I have seen this error when I changed the DNS entries on the General tab. I think I remember seeing the Kea service stopped after that. I was unable to start the Kea server again until I killed its process from the command line.
-
@cmcdonald Did you ever find a fix for this. I am having massive issues with the KEA DHCP services. Service Watchdog is causing the error as it tries to restart the service and initiates a lock file, but the service does not start properly and when it tries again, if cannot remove the other lock file. My particular issue is that when KEA starts acting up, and the service get restarted, if there is a multiple failure in a row situation, I lose the ability to pass traffic and have to completely reboot the device. I have yet to figure out just WHAT is causing the service to restart multiple times in a row in succession, but I suspect that the older KEA instance the CE is running may be the culprit. I am waiting, in great anticipation, for the new CE version to be release and hoping for a fix in there with the newer underlying OS and fixes.
In the meantime, if anyone else is experiencing the system hang and restarting of KEA, please let me know if you have figured out a fix as it is causing a lot of frustration losing Internet in the middle of the business day.
-
@jeffry-maynard said in Kea server is down:
let me know if you have figured out a fix
You are using ... 2.7.2 ?
Afaik, there was a small patch avaible since the beginning to solve this situation.
Or, even better : 2.8.0 beta is out now for several weeks, and it look very promising,
