You can certainly see messages in the logs if you setup the ha logs
(see: https://kea.readthedocs.io/en/kea-2.2.0/arm/logging.html and in
particluar this chart
https://kea.readthedocs.io/en/kea-2.2.0/arm/logging.html#id3 which
shows all of the available loggers - you will want to for sure setup
"ke
ok Thanks for confirmation Darren
On Mon, Mar 6, 2023 at 4:16 PM Darren Ankney
wrote:
> neither of those configs are valid. Looks like ChatGPT made up some
> things there. See:
>
> https://kea.readthedocs.io/en/kea-2.2.0/arm/hooks.html#ha-high-availability-outage-resilience-for-kea-servers
>
Yes Thanks Darren, found the issue after changing the file name it is
working fine and do you have any idea like how can we get the failover
status
In ISC DHCP failover we can see them in the lease file (communication
interrupted, recover, partner-downetc) with the failover name
being specified
Looks like your socket locations don't match between the kea config
and the ctrl agent configuration. Those are filenames, so they are
going to need to match exactly. Kea is in the driver's seat there as
it actually creates the file. the ctrl agent "talks" to kea through
such file.
example, you
neither of those configs are valid. Looks like ChatGPT made up some
things there. See:
https://kea.readthedocs.io/en/kea-2.2.0/arm/hooks.html#ha-high-availability-outage-resilience-for-kea-servers
Take a look at hot-standby as that is the easiest mode to configure and operate.
On Mon, Mar 6, 20
Hi All,
I am trying to configure the kea-HA setup in my local environment but I am
facing an issue the heartbeat is getting failed and the logs are as follows:
Logs on Failover
=
2023-03-06 09:04:43.761 DEBUG [kea-dhcp4.http/28550.140575742654656]
HTTP_CLIENT_REQUEST_SEND sending HTTP
