[Kea-users] HA partner suddenly goes into 'terminated' state

[Elton, Norman N]

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<https://www.facebook.com/wminfotech> | Twitter<https://twitter.com/wminfotech> | Instagram<http://www.instagram.com/wminfotech>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20250609/cec36d34/attachment.htm>