[stork-users] Stork dhcp6 internal server error: number overflow

[Marek Hajduczenia]

It is a known bug - please search the list of issues against Stork.

On Tue, May 14, 2024 at 11:55 AM Justin Krejci <JKrejci at usinternet.com>
wrote:

> I just recently upgraded my stork server and dhcp server to Ubuntu 24.04
> LTS.
> I also refreshed the stork server app and the stork agent apps to the
> latest via ISC apt repo.
>
> *DHCP Server (**Kea - 2.4.1)*
> Package: isc-stork-agent
> Version: 1.16.0.240405082622
>
> *Stork Server*
> Package: isc-stork-server
> Version: 1.16.0.240405082626
>
>
> The stork server is showing this in the web event logs
>  2024-05-14 11:59:16
>  processing Kea command by daemon [6] dhcp6 on machine [2] 216.17.94.7
> failed
>  internal server error: unable to parse server's answer to the forwarded
> message: Number overflow: 18446744073709486065 in :0:210
>
>
> After about 15-20 seconds I get this
>  2024-05-14 11:59:36
>  processing Kea command by daemon [6] dhcp6 on machine [2] 216.17.94.7
> succeeded
>
>
> This just repeats every minute. The error and overflow number are
> identical every time.
> There is only 1 DHCP server talking to the Stork server.
>
> I haven't been using these servers for a while before the upgrade so I am
> not sure if it was behaving this way before the upgrade or if this is new
> behavior since the upgrade.
> I tried full server reboots of both DHCP and Stork server machines.
> If I push the "Get Latest State" button in Stork for the Kea machine, it
> successfully completes.
> I tried removing and re-authorizing the Kea machine in the Stork server.
>
> Is this a config issue?
> Stork bug?
> Ubuntu issue (it's the newest LTS release)
> How best should I troubleshoot further?
>
> Thank you!
> Justin
>
> --
> Stork-users mailing list
> Stork-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/stork-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20240514/ce4b4fd1/attachment.htm>