Hello splge,
Can you confirm whether the slapd setup where you encountered this crash
might have included a global/frontend instance of the dynlist overlay?
If you still have the logs, can you show a crash report from dmesg?
See additional context quoted below. I would like to know for sure
whether you and wouldsmina are talking about the same crash.
Thank you,
Ryan
On Wed, Jan 24, 2024 at 08:02:49AM -0800, Quanah Gibson-Mount wrote:
--On Wednesday, January 24, 2024 3:07 PM +0100 wouldsmina
<wouldsm...@gmail.com> wrote:
Hello,
I am experiencing the same issue. Here are the logs I obtain in the
syslog:
2024-01-24T09:38:16.810558+01:00 ldap kernel: [ 1553.168747]
slapd[13335]: segfault at 0 ip 00007fc2370b49c1 sp 00007fbd359fc0c0 error
4 in dynlist-2.5.so.0.1.8[7fc2370b1000+6000] likely on CPU 1 (core 0,
socket 2)
2024-01-24T09:38:16.810568+01:00 ldap kernel: [ 1553.168761] Code: 48 29
d0 48 89 d7 48 89 c1 31 c0 83 c1 6c c1 e9 03 f3 48 ab 48 8b 84 24 10 02
00 00 4c 89 ef c7 84 24 a0 00 00 00 03 00 00 00 <48> 8b 00 ff 50 78 44 39
73 64 74 09 45 84 e4 0f 85 22 03 00 00 48
2024-01-24T09:38:16.840012+01:00 ldap slapd[13342]: Stopping OpenLDAP:
slapd.
To reproduce, simply activate the dynlist module and try to make an LDAP
query. In slapd.conf add:
moduleload dynlist
overlay dynlist
Likely <https://bugs.openldap.org/show_bug.cgi?id=10091>.
--Quanah
