https://bugs.openldap.org/show_bug.cgi?id=9754
Issue ID: 9754 Summary: segfault after adding olcAccess Product: OpenLDAP Version: 2.6.0 Hardware: x86_64 OS: Linux Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: slapd Assignee: bugs@openldap.org Reporter: goudal@enseirb.fr Target Milestone: ---
On a new production server 2.6.0 on ubuntu 20.04 LTS uptodate. After adding an olcAccess attribute I got a segfault. The aclValue added is {9}to attrs=ipbCompteValide,ipbEtendue,mailForwardingAddress by dn.base="uid=cptadmin,ou=people,dc=ipb,dc=fr" write by * read
(the ipbXXX attrs are local ones).
I have tried to add it twice and it did segfault twice.
Here are the last logs for the server (logLevel was on sync).
Nov 25 14:34:32 ldap2021 slapd[67824]: slap_graduate_commit_csn: removing 0x7f3a475615c0 20211125133351.609580Z#000000#00a#000000 Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291397 MOD dn="dc=ipb,dc=fr" Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291397 MOD attr=contextCSN Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291397 syncprov_matchops: recording uuid for dn=dc=ipb,dc=fr on opc=0x7f3a48001440 Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1053 op=1 syncprov_qresp: set up a new syncres mode=2 csn= Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291397 RESULT tag=103 err=0 qtime=0.000017 etime=0.003762 text= Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291398 SRCH base="dc=ipb,dc=fr" scope=2 deref=0 filter="(entryUUID=29a4991c-9dda-103b-98c2-c3fe49d4fff9)" Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291398 SRCH attr=* + Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291398 SEARCH RESULT tag=101 err=0 qtime=0.000028 etime=0.000285 nentries=1 text= Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291399 MOD dn="uid=pbouchevrea,ou=people,dc=ipb,dc=fr" Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291399 MOD attr=ipbDateFin entryCSN modifiersName modifyTimestamp Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291399 syncprov_matchops: recording uuid for dn=uid=pbouchevrea,ou=people,dc=ipb,dc=fr on opc=0x7f3a48001630 Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291399 syncprov_findbase: searching Nov 25 14:34:32 ldap2021 slapd[67824]: slap_queue_csn: queueing 0x7f3a438bc700 20211125133351.654596Z#000000#00a#000000 Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1053 op=1 syncprov_qresp: set up a new syncres mode=2 csn=20211125133351.654596Z#000000#00a#000000 Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291399 RESULT tag=103 err=0 qtime=0.000025 etime=0.022224 text= Nov 25 14:34:32 ldap2021 slapd[67824]: slap_graduate_commit_csn: removing 0x7f3a438bc700 20211125133351.654596Z#000000#00a#000000 Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291400 MOD dn="dc=ipb,dc=fr" Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291400 MOD attr=contextCSN Nov 25 14:34:32 ldap2021 slapd[67824]: conn=1000 op=291400 syncprov_matchops: recording uuid for dn=dc=ipb,dc=fr on opc=0x7f3a50003440 Nov 25 14:34:32 ldap2021 kernel: [262778.995540] slapd[68072]: segfault at 0 ip 00007f4ea0d3553e sp 00007f4e9dae9f48 error 4 in libc-2.31.so[7f4ea0cad000+178000] Nov 25 14:34:32 ldap2021 kernel: [262778.995584] Code: b6 07 29 c8 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d c0 0f 00 00 0f 8f 74 02 00 00 <f3> 0f 6f 0f f3 0f 6f 06 66 0f 74 c1\ 66 0f da c1 66 0f ef c9 66 0f Nov 25 14:34:36 ldap2021 slapd[70083]: * Stopping OpenLDAP slapd
https://bugs.openldap.org/show_bug.cgi?id=9754
--- Comment #1 from Ondřej Kuzník ondra@mistotebe.net ---
On a new production server 2.6.0 on ubuntu 20.04 LTS uptodate. After adding an olcAccess attribute I got a segfault. The aclValue added is {9}to attrs=ipbCompteValide,ipbEtendue,mailForwardingAddress by dn.base="uid=cptadmin,ou=people,dc=ipb,dc=fr" write by * read
(the ipbXXX attrs are local ones).
I have tried to add it twice and it did segfault twice.
Here are the last logs for the server (logLevel was on sync).
Please provide simplified configs (or at least sanitised to remove passwords) and a way to reproduce.
All crash reports should also provide a gdb backtrace, if unsure how to generate one, see the related FAQ entry to assist you: https://www.openldap.org/faq/data/cache/59.html
Regards,
https://bugs.openldap.org/show_bug.cgi?id=9754
--- Comment #2 from goudal@enseirb.fr --- Hello,
I understand what you ask, but I can't do it, as I said it's a production server so I can't play with it. Sorry.
https://bugs.openldap.org/show_bug.cgi?id=9754
--- Comment #3 from Ondřej Kuzník ondra@mistotebe.net --- On Fri, Nov 26, 2021 at 02:33:23PM +0000, openldap-its@openldap.org wrote:
I understand what you ask, but I can't do it, as I said it's a production server so I can't play with it.
Hi, you should be able to arrange for the operating system to save the core file from the crash and then you'll be able to analyse it in gdb. The logs you provided do not seem to correlate with a cn=config change anyway.
Regards,
https://bugs.openldap.org/show_bug.cgi?id=9754
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs_review | Status|UNCONFIRMED |RESOLVED Resolution|--- |FEEDBACK
--- Comment #4 from Quanah Gibson-Mount quanah@openldap.org --- Need reproduction steps or backtrace from core file.