[stork-users] [SPAM] Re: Problems to monitor the DHCP4 Daemon after the Stork 2.4.0 update

[Peters Vincent]

Hi Slawek

I now specified an additional HTTP control Socket for both of our Servers:
{
    "socket-type": "http",
    "socket-address": "127.0.0.1",
    "socket-port": 8004
  }

Now it works!
Do we need for an update/patch of stork or can we just leave it like that.

Greetings
_________________________________________  
Vincent Peters

Stadt Chur
  
-----Ursprüngliche Nachricht-----
Von: Slawek Figiel <slawek at isc.org> 
Gesendet: Montag, 9. März 2026 16:42
An: Peters Vincent <Vincent.Peters at chur.ch>; stork-users at lists.isc.org
Betreff: [SPAM] Re: [stork-users] Problems to monitor the DHCP4 Daemon after the Stork 2.4.0 update

Hello Vincent!

The problem is related to the default socket permissions in Kea: 
kea#4260 (closed), and to introducing support for the direct Kea API in Stork.

Stork no longer communicates with the DHCP daemons through the Kea CA. 
Instead, it establishes a direct connection to them. It uses the endpoints specified in the control-sockets property of the Kea configuration. By default, the only specified control socket is a Unix socket. Unfortunately, the socket file is created with permissions that grant write access only to the owner. So, the Stork agent user cannot write to it.

See discussion in: https://gitlab.isc.org/isc-projects/stork/-/issues/2318.

As a workaround, you can specify an additional HTTP control socket for Stork purposes. See https://kea.readthedocs.io/en/stable/arm/dhcp4-srv.html#http-https-control-socket
for details.

Feel free to ask questions if you have any configuration troubles. If it doesn't help, please, attach Stork server and agent logs.

Regards,
Slawek Figiel
Software Developer
ISC

On 3/9/26 4:37 PM, Peters Vincent wrote:
> Hello Together
> 
> We have a Problem with the new 2.4.0 update. We did the updates for 
> the Agents and the Server. Everything is still functioning.
> 
> But – We can't monitor the DHCP4 Daemon anymore "There is a 
> communication issue with the daemon."
> 
> When we hover over the error on the dashboard it says:
> Communication with the daemon on this machine is broken. The Stork 
> Agent and Kea Control Agent appear to be working, but the daemon 
> behind it is not responding or responds with errors. The last 1131 
> attempt(s) to communicate with the daemon failed. Please make sure 
> that the daemon is up and is reachable
> 
> Bind works perfectly fine and had no problem with the communication 
> after the update.
> 
> 
> We also saw after the update two dhcp4 Daemons for each server. The 
> same for the Bind Daemon.
> 
> 
> Versions:
> 
> Server1:
> 
>              Kea: 3.0.2
> 
>              Bind: 9.20.18
>              Agent: 2.4.0
> 
> Server2:
> 
>              Kea: 3.0.2
> 
>              Bind: 9.20.18
>              Agent: 2.4.0
> 
> 
> We tried to deregister and register it again, but that didn't help us out.
> 
> Is this a real Problem or do we need to change some config after the update?
> 
> Greetings
> _________________________________________
> *Vincent Peters*
> 
> *Stadt Chur*
> 
>