[Kea-users] Kea6 random segmentation fault

Andreas ml+dhcp at tibdefender.com
Mon Jul 27 10:59:58 UTC 2026


Dear list,


since Friday we're experiencing random and unexplainable Segmentation 
Faults on kea6-server. We're running a 2-node hot-standby HA setup with 
kea 3.0.3 since a few weeks and without any issues. Both the kea4 and 
kea6 server are running on the same machine, stork-agent running in 
parallel. kea6 is serving IA_NA and PD to about 15k clients.

It first happened on the current primary node:

2026-07-24T16:50:46.930672+02:00 kea-dhcp-01 kernel: kea-dhcp6[3923430]: 
segfault at 7f3993e79ba1 ip 00007f3edee784cc sp 00007f3ec7023870 error 4 
in libkea-dhcp.so.109.0.0[e44cc,7f3edee02000+fc000] likely on CPU 1 
(core 0, socket 0)
2026-07-24T16:50:46.930681+02:00 kea-dhcp-01 kernel: Code: 48 89 ac 14 
90 00 00 00 48 8b 68 e8 48 01 dd 80 bd e1 00 00 00 00 0f 84 f2 01 00 00 
49 8b 04 24 c6 85 e0 00 00 00 30 4c 89 e7 <ff> 50 38 0f b7 f0 49 8b 04 
24 48 8d 15 b3 c1 ff ff 48 8b 40 40 48
2026-07-24T16:50:46.934788+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Main process exited, code=killed, 
status=11/SEGV
2026-07-24T16:50:46.934891+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Failed with result 'signal'.
2026-07-24T16:50:46.935103+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Consumed 44min 56.757s CPU time, 2.7G 
memory peak.

2026-07-24T18:00:46.279228+02:00 kea-dhcp-01 kernel: kea-dhcp6[4121537]: 
segfault at 7face69e9991 ip 00007fabb69594cc sp 00007fab9bac7870 error 4 
in libkea-dhcp.so.109.0.0[e44cc,7fabb68e3000+fc000] likely on CPU 0 
(core 0, socket 0)
2026-07-24T18:00:46.279236+02:00 kea-dhcp-01 kernel: Code: 48 89 ac 14 
90 00 00 00 48 8b 68 e8 48 01 dd 80 bd e1 00 00 00 00 0f 84 f2 01 00 00 
49 8b 04 24 c6 85 e0 00 00 00 30 4c 89 e7 <ff> 50 38 0f b7 f0 49 8b 04 
24 48 8d 15 b3 c1 ff ff 48 8b 40 40 48
2026-07-24T18:00:46.284805+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Main process exited, code=killed, 
status=11/SEGV
2026-07-24T18:00:46.284892+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Failed with result 'signal'.
2026-07-24T18:00:46.284933+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Consumed 2min 13.601s CPU time, 895.2M 
memory peak.

2026-07-24T18:30:46.911312+02:00 kea-dhcp-01 kernel: kea-dhcp6[4130306]: 
segfault at 7f94e43ff ip 00007f955e0a44cc sp 00007f9543251870 error 4 in 
libkea-dhcp.so.109.0.0[e44cc,7f955e02e000+fc000] likely on CPU 2 (core 
1, socket 0)
2026-07-24T18:30:46.911326+02:00 kea-dhcp-01 kernel: Code: 48 89 ac 14 
90 00 00 00 48 8b 68 e8 48 01 dd 80 bd e1 00 00 00 00 0f 84 f2 01 00 00 
49 8b 04 24 c6 85 e0 00 00 00 30 4c 89 e7 <ff> 50 38 0f b7 f0 49 8b 04 
24 48 8d 15 b3 c1 ff ff 48 8b 40 40 48
2026-07-24T18:30:46.917777+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Main process exited, code=killed, 
status=11/SEGV
2026-07-24T18:30:46.917892+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Failed with result 'signal'.
2026-07-24T18:30:46.917940+02:00 kea-dhcp-01 systemd[1]: 
isc-kea-dhcp6-server.service: Consumed 39.436s CPU time, 889.6M memory peak.

We restarted it several times, removed the syslogging, stopped 
stork-agent to make sure it is not affected by any external source. But 
as nothing helped we decided to leave it as is, stop the kea6 daemon and 
run the other node as primary.

This also worked fine till Sunday where we hit this:
2026-07-26T12:19:21.136022+02:00 kea-dhcp-02 kernel: traps: 
kea-dhcp6[1460682] general protection fault ip:7f3636047af5 
sp:7f36221deaa0 error:0 in libkea-dhcp.so.109.0.0[e4af5,7f3635fd1000+fc000]
2026-07-26T12:19:21.139318+02:00 kea-dhcp-02 systemd[1]: 
isc-kea-dhcp6-server.service: Main process exited, code=killed, 
status=11/SEGV
2026-07-26T12:19:21.139488+02:00 kea-dhcp-02 systemd[1]: 
isc-kea-dhcp6-server.service: Failed with result 'signal'.
2026-07-26T12:19:21.139621+02:00 kea-dhcp-02 systemd[1]: 
isc-kea-dhcp6-server.service: Consumed 1h 30min 159ms CPU time, 2.1G 
memory peak.

Are there any known issues in version 3.0.3 that could explain this?

Thanks in advance!


BR

Andreas


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20260727/c0803987/attachment.htm>


More information about the Kea-users mailing list