Hi Francis,
Thanks for the feedback. Your first point seems like the best practice
implementation, although in practice just using a dummy MAC for a
blocked-out address will work well enough.
We manage reservations through an external application talking to MySQL
directly, and so don't store rese
On Mon, 18 Jun 2018 16:10:16 -0400
Thomas Markwalder wrote:
> Hello:
>
> What is occurring is that kea-ctrl-agent is attempting to execute the
> command, and since it does not have a lease mgr, the command fails. The
> lease-cmds hooks library should be loaded by kea-dhcp4 and kea-dhcp6,
> n
Hello:
What is occurring is that kea-ctrl-agent is attempting to execute the
command, and since it does not have a lease mgr, the command fails. The
lease-cmds hooks library should be loaded by kea-dhcp4 and kea-dhcp6,
not the control agent. Currently, none of our hook libraries should be
lo
I am currently using postgresql lease storage for hdcpv6 and dhcpv4.
When attempting to delete a lease using lease command hook library, I
get the following reply:
[ { "result": 1, "text": "no current lease manager is available" } ]
Does this only work with memfile, or am I doing somethin
On 06/18/2018 05:03 AM, Satish Patel wrote:
> Thanks you for comments, I told you half story, full story is we have two kea
> instance for HA and they are pointed to galera DB cluster for centralize
> Shared DB.
>
> Both node active and inserting records in cluster DB and everything works but
>
Thanks you for comments, I told you half story, full story is we have two kea
instance for HA and they are pointed to galera DB cluster for centralize Shared
DB.
Both node active and inserting records in cluster DB and everything works but
every few hour node-2 kea is dying with mentioned erro
On 18/06/2018 01:07, Satish Patel wrote:
> I have configured kea 1.3.0 with mysql and everything works but after
> few hours found kea is dead and spotted following error in log, I have
> check everything mysql running fine everything looks good in DB.
>
> 2018-06-15 11:48:55.798 INFO [kea-dhcp4.
Satish Patel writes:
> h.host_id, o.option_id>, reason: MySQL server has gone away (error
> code: 2006). Server exiting now!
=> it is a MySQL error so not a Kea one, but I have 2 extra comments:
- google gave an idea: increase the maximum packet setting in MySQL
(I am afraid it won't solve the p
