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

[Peters Vincent]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20260309/318a8861/attachment.htm>