[stork-users] Stork agent doesn't detect listening ip host

[Marcin Siodelski]

Hello Pierre-Olivier,

Thank you for sending your email and trying the new Stork version.
Unfortunatelly, it seems that you found a bug which was accidentally
introduced when we reworked the command line options for this release.
This was a major rework related to the introduction of the TLS between
the server and the agent and apparently this slipped through our tests.

I tried to find a workaround for this issue but apparently there is no
viable one. I have a fix for it, which I can offer as a code patch but
that would require that you build the agent on your own rather than use
the packages.

You also have to be aware that we have changed the way the agents are
now connected to Stork. The details can be found here:

https://gitlab.isc.org/isc-projects/kea/-/issues?milestone_title=None&scope=all&sort=created_asc&state=opened&utf8=%E2%9C%93

Marcin Siodelski
Sr. Software Engineer,
ISC

W dniu 04.03.2021 o 16:34, Pierre-Olivier MORILLON pisze:
> Hello,
> 
> I am on a centos 7 environment.
> 
> Since I upgraded my stork agents to version 0.15 on my kea servers, they
> no longer detect the IP on which I ask them to listen.
> 
> This is what I get when I launch the program manualy :
> 
> 
> [root at keav6  ~]#stork-agent --host 10.0.29.20 --port 8081
> INFO[2021-03-04 16:18:46]             main.go:23    Starting Stork
> Agent, version 0.15.0, build date 2021-03-02 14:58
> INFO[2021-03-04 16:18:46]  promkeaexporter.go:268   Prometheus Kea
> Exporter listening on :9547, stats pulling interval: 10 seconds
> INFO[2021-03-04 16:18:46]          monitor.go:84    Started app monitor
> INFO[2021-03-04 16:18:46]          monitor.go:152   new or updated apps
> detected:
> INFO[2021-03-04 16:18:46]          monitor.go:159      kea: control:
> 192.168.254.203:8080
> WARN[2021-03-04 16:18:46]              kea.go:57    skipped refreshing
> viewable log files because config-get returned non success result
> INFO[2021-03-04 16:18:46]prombind9exporter.go:821   Prometheus BIND 9
> Exporter listening on :9119, stats pulling interval: 10 seconds
> INFO[2021-03-04 16:18:46]            agent.go:431   started serving
> Stork Agent                   address="[::]:8081"
> WARN[2021-03-04 16:18:56]  promkeaexporter.go:367   problem with
> connecting to dhcp daemon: forwarding socket is not configured for the
> server type dhcp4
> 
> 
> As you can see, the system takes into account the requested port but not
> the listening IP address, it takes the default one which is 0.0.0.0 all
> the time.
> This is also visible on my nestat where I can see it:
> tcp6    0    0 :::8081     :::*         LISTEN         14859/stork-agent
> 
> 
> The problem is the same when I launch the stork-agent with the deamon.
> 
> Do you have an idea of the problem?
> 
> 
> Thanks,
> PO
> 
>