[Kea-users] No 2.6.5 for Debian Trixie amd64?

[Darren Ankney]

Hi Stefan,

> But from the webgui it seems to use the unix socket ... but the HA
status only changed to looking OK after adding the http-socket (with IP
127.0.0.1 and port 8000, btw)

Can you share the HA configuration?  Adding http-socket in the
"control-sockets" section shouldn't have anything to do with HA unless
you have done something special in the HA hook configuration.

Thank you,
Darren Ankney

On Fri, May 15, 2026 at 12:15 PM Stefan G. Weichinger <lists at xunil.at> wrote:
>
> Am 15.05.26 um 17:19 schrieb Darren Ankney:
> > Hi Stefan,
> >
> >> Should I remove the unix socket?
> >
> > You should either use the unix socket or the http socket but not both.
> >
> >> Should the CA now be disabled on the nodes?
> >
> > Yes, you should shut down and disable the CA.
> >
> >> Do I have to configure Stork somewhere to actually access this socket on 10.0.0.230:8004 ?
> >
> > The stork-agent should figure this out from reading your
> > kea-dhcp4.conf.  I don't believe there is a way to force it to do so.
> > If the CA is running also, the stork-agent will probably be confused
> > by this and likely you will see multiple kea daemons showing up in the
> > Stork UI.
>
> Thank you, Darren, for the clear instructions.
>
> Right now everything is green and running, so I won't touch it anymore
> today ...
>
> But from the webgui it seems to use the unix socket ... but the HA
> status only changed to looking OK after adding the http-socket (with IP
> 127.0.0.1 and port 8000, btw)
>
> It's a bit confusing for me as I am not always thinking about the inner
> structure of my kea-cluster(s). Mostly it just works and I forget it for
> a while.
>
> I will maybe try something tomorrow.
>