This happens to us, too, using a shared MySQL backend for our
lease/reservation DBs.
I put Monit up on our Kea backends to automatically restart when it detects
that the process isn't running, and with a bit of tweaking, it's been
pretty bulletproof, with a bonus of handling other, unrelated crash
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
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.dhcp4/16020] DHCP4_STARTED
Kea DHCPv4 server versi
