[Kea-users] kea 1.3.0 dying with mysql error

[Satish Patel]

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 error, everything same node dying. Node-1 never had any issue. 

Do you think this is clustering issue they both trying to do same thing and one of node dying? I have check network and every possible thing but  nothing wrong there, also I have increase max_packet_size in db but no luck :(

Sent from my iPhone

> On Jun 18, 2018, at 7:29 AM, Tomek Mrugalski <tomasz at isc.org> wrote:
> 
>> 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.dhcp4/16020] DHCP4_STARTED
>> Kea DHCPv4 server version 1.3.0 started
>> 2018-06-15 12:01:29.048 ERROR [kea-dhcp4.dhcpsrv/16020]
>> DHCPSRV_MYSQL_FATAL_ERROR Unrecoverable MySQL error occurred: unable
>> to execute for <SELECT h.host_id, h.dhcp_identifier,
>> h.dhcp_identifier_type, h.dhcp4_subnet_id, h.dhcp6_subnet_id,
>> h.ipv4_address, h.hostname, h.dhcp4_client_classes,
>> h.dhcp6_client_classes, h.dhcp4_next_server, h.dhcp4_server_hostname,
>> h.dhcp4_boot_file_name, o.option_id, o.code, o.value,
>> o.formatted_value, o.space, o.persistent FROM hosts AS h LEFT JOIN
>> dhcp4_options AS o ON h.host_id = o.host_id WHERE h.dhcp4_subnet_id =
>> ? AND h.dhcp_identifier_type = ?    AND h.dhcp_identifier = ? ORDER BY
>> h.host_id, o.option_id>, reason: MySQL server has gone away (error
>> code: 2006). Server exiting now!
> Translation to plain English: MySQL server has gone away (i.e. Kea
> connection to MySQL server was terminated for whatever reason, DB
> restart, temporary network failure, etc).
> 
> In this state Kea would be useless. It would not be able to answer any
> packets as it couldn't check lease state, create new leases, extend
> existing ones etc. Continuing in this state would give users a false
> impression that the server is somehow functional. Therefore kea 1.3
> terminates itself as soon as database failure is detected.
> 
> This has been improved in 1.4. Kea attempts to reconnect. If this
> behavior makes you unhappy, please upgrade.
> 
>> 2018-06-15 12:01:29.055 INFO  [kea-dhcp4.legal-log/16020]
>> LEGAL_LOG_FILE_CLOSED  @@Missing placeholder %1 for
>> '/var/log//kea-forensic4.20180615.txt'@@
> This is begign bug in our logging routines. I've submitted bug #5653 for
> this. You can view (and possibly comment on it if you like) here:
> https://kea.isc.org/ticket/5653
> 
> Tomek
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users