[stork-users] Error: Cannot get state of machine

[Kevin P. Fleming]

On Wed, Jul 6, 2022 at 9:26 AM John Gammon <john.gammon at forkeddeer.com>
wrote:

> Kevin,
>
> Thank you for the reply last evening.  I have a small TESTBENCH, which is
> an air-gapped network, for testing Kea with Stork.  My environment is
> comprised and configured with:
>
>    1. A single router (6.6.6.1)
>       1. wired ports (x4)
>       2. wireless availablility (disabled at this time)
>    2. A single server (6.6.6.2)
>       1. Ubuntu Server 20.04.4 LTS
>       2. Kea running
>          1. dhcp4
>          2. ddns
>       3. A Postgresql db instance
>          1. dhcpdb
>          2. ddnsdb
>          3. stork
>       4. Stork server running
>       3. A single listener/satellite (6.6.6.3)
>       1. Ubuntu Server 20.04.4 LTS
>       2. Kea listener running
>       3. Stork agent running
>
>
> By 'Kea listener' do you mean the Kea control agent? That should be
colocated on the machine where the Kea DHCP services are running, otherwise
it won't be able (easily) to talk to those services. As it is now, the
Stork server will reach out to the Stork agent on another machine, which
will talk to the Kea control agent on the same machine, which would then
talk to the Kea DHCP4 daemon back on the first machine.

In the configuration you posted previously you had the server configured to
reach the agent on 6.6.6.2, but in the listing above the agent is listening
on 6.6.6.3.

In order to simplify things I suspect you may want to reorganize a bit:

* One server should have the Kea DHCP4 daemon, the Kea control agent, and
the Stork agent. That server is your 'DHCP server', with the necessary bits
to be able to monitor it.

* One server should have the Stork server, so that server is your
'monitoring server'.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20220706/12b2b747/attachment.htm>