kea crashing ?

grandrivers

wathdog kept re starting kea in 25.03.b.20250427.2348 I had to roll back to 25.03-BETA (amd64)
built on Mon Apr 14 14:38:00 EDT 2025 didnt see anything obvious in syslog kea needs its own section

marcosm

Kea restarting isn't necessarily incorrect. It may have been part of a service restart due to some other event. The full system and DHCP logs covering the event are needed. Additionally Kea can be removed/disabled from the watchdog service to see if it's indeed crashing and not recovering, or simply being restarted by something else.

grandrivers

@marcosm
I will have to dig into more it kea never was coming up looked into it a bit but got frustrated and gave up, rolled back using boot environments .Main gpog down and flapping with no restore insight field techs opened noc ticket

Gertjan

@grandrivers

Kea restarting ?
Let's check :

[25.03-BETA][root@pfSense.bhf.tld]/root: ps aux | grep 'kea'
root    52082   0.0  0.1  14236   2924 u0  IC+  16Apr25     0:00.14 tail -f /var/log/kea-ddns.log
root    25279   0.0  0.6  50424  24764  1- S    21Apr25     2:24.11 /usr/local/sbin/kea-dhcp4 -c /usr/local/etc/kea/kea-dhcp4.conf
root    27417   0.0  0.6  47824  24464  1- S    21Apr25     1:09.93 /usr/local/sbin/kea-dhcp6 -c /usr/local/etc/kea/kea-dhcp6.conf

The reason why it restarted last 21 April : that was me.

Btw : I'm using 25_03_b_20250306, the beta 2 version on a SG 4100.
( and going to beta 3 this morning ).
Using IPv4 and IPv6 (tracking) on my LANs - the IPv6 prefixes 'never' change. This could/will ? be a restart reason.
All my 3 LAN interfaces are hooked up to switches that are also UPS powered, which means these interfaces never go 'down'. That will be a restart reason.

grandrivers

everything seems fine now that main wan is not flapping or manually set to down