[stork-users] Issues with stork-agent

[David Rickard]

Slawek

> The Stork agent produces messages about a problem connecting to some 
> daemons and skipping their logs fetch because your Kea CA configuration 
> specifies some daemons that are not running.
> The Stork agent scans the Kea CA config first and then looks for the Kea 
> daemons. In your case, the config specifies control sockets for the 
> DHCPv4, DHCPv6, and D2 daemons. The last two are probably not running in 
> your environment.
>
> To fix the problem, remove the unnecessary entries from the 
> `control-sockets` node in the Kea CA config.

OK, that makes a lot of sense. I hadn't considered removing those lines, so I think your open issue makes sense. Hopefully that'll save somebody else from filling their logs too! Having changed it, there's no longer those event logs, so that does appear to have resolved everything.

Many thanks for all your help, it has been most invaluable.

Regards

David Rickard