Hi Norman, It is possible for more than clock skew to cause this. Here are a couple of examples:
- https://gitlab.isc.org/isc-projects/kea/-/issues/2223 - https://gitlab.isc.org/isc-projects/kea/-/issues/2932 Look for log messages like this: Jun 12 15:05:39 dhcp-1 kea-dhcp4[564812]: WARN [kea-dhcp4.ha-hooks.139625701795584] HA_LEASE_UPDATE_CONFLICT [hwtype=1], cid=[], tid=0x0: lease update to standby-dhcp (http://dhcp-2:8001/) returned conflict status code: ResourceBusy: IP address:123.123.123.123 could not be updated. (error code 4) Jun 12 15:05:39 dhcp-1 kea-dhcp4[564812]: WARN [kea-dhcp4.ha-hooks.139625718580992] HA_LEASE_UPDATE_CONFLICT [hwtype=1], cid=[], tid=0x0: lease update to standby-dhcp (http://dhcp-2:8001/) returned conflict status code: ResourceBusy: IP address:123.123.123.123 could not be updated. (error code 4) If you are seeing: ResourceBusy then you probably want to enable lease caching: https://kea.readthedocs.io/en/kea-2.6.3/arm/dhcp4-srv.html#lease-caching which SHOULD mitigate the issue (assuming it is the same cause as issue 2932. If it is the same cause as 2223, then perhaps not). Thank you, Darren Ankney On Mon, Jun 9, 2025 at 9:13 AM Elton, Norman N <wne...@wm.edu> wrote: > > We’ve got HA pairs of Kea servers, running 2.4.2. When I update the > configuration, I use the API to issue a “config-reload” command. This has > worked fine. > > Occasionally, the configuration reloads, but the peer server mysteriously > drops into a “terminated” HA state. The first server, whose configuration was > reloaded, begins complaining: > > HA_TERMINATED_RESTART_PARTNER waiting for the partner in the TERMINATED state > to be restarted > > This is resolved by reloading the configuration of the peer. But it’s spooky > that DHCP processing has stopped on the first server. According to the > documentation I’ve found, the terminated state is reached when the two > servers have a large clock skew. I’ve confirmed both have the accurate time, > and there are no warning messages about clock skew. > > Has anyone experienced this before? I’ve got a bug open > (https://gitlab.isc.org/isc-projects/kea/-/issues/3928). > > Thanks > > Norman > > > Norman Elton > > Director, IT Infrastructure > > William & Mary > > > > Stay connected with W&M IT: Facebook | Twitter | Instagram > > > > -- > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
