The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here.
If you plan to attach anything you don't want to be publicly viewable,
make sure you the confidential checkbox.
> * Mysql backend on separate server
> * ~300 leases total
> * 3 months of up time
> * ~4 host reservations
> * Using Flex ID to change client ID to option 82 identifier
> * Using DDNS to strip bad hostname characters
> * Sql connection wait timer set to 10000
> * Dhcp socket type set to udp
> o Was RAW when issue occurred.
Thanks for sharing this information. That doesn't look like a
particularly stressful or complex configuration. When opening a bug
report, please also include the following crucial information:
- which kea version you used
- what OS (linux of bsd distro, which version)
- whether you compiled Kea from release tarball, got it from a package
or perhaps got source from git
- include your full config file (removing database passwords is
This should be all covered by the bug_report template in gitlab.
> Segfault error from journctl:
> *Feb 09 01:49:03 harpy kernel: kea-dhcp4: segfault at 10 ip
> 00007fabaad99918 sp 00007fff8ff4b690 error 4 in
Sadly, this information is useless if we don't have extra information.
Is there a core dump? If there is, please attach the core dump to the