openldap-bugs March 2021

openldap-bugs@openldap.org

1 participants
317 discussions

[Issue 9337] New: Slapd crash with lastbind overlay
by openldap-its＠openldap.org 10 May '21

10 May '21

https://bugs.openldap.org/show_bug.cgi?id=9337 Issue ID: 9337 Summary: Slapd crash with lastbind overlay Product: OpenLDAP Version: 2.4.50 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: frederic.poisson(a)admin.gmessaging.net Target Milestone: --- Hello, I have an issue with a 2.4.50 OpenLDAP instance configured with replication (1 master and 1 replica), and when i activate the lastbind overlay. The replica server crash like this : slapd[8433]: segfault at 1d0 ip 000000000049f70b sp 00007f189f7fd1a0 error 4 in slapd[400000+1d8000] The database is this one with overlay loaded : dn: cn=module{0},cn=config olcModuleLoad: {0}sssvlv.la olcModuleLoad: {1}ppolicy.la olcModuleLoad: {2}syncprov.la olcModuleLoad: {3}lastbind.la olcModuleLoad: {4}pw-sha2.la dn: olcDatabase={3}mdb,cn=config objectClass: olcDatabaseConfig objectClass: olcMdbConfig olcUpdateRef: ldap://master.server:389/ If i add this configuration it crash : dn: olcOverlay={2}lastbind objectClass: olcOverlayConfig objectClass: olcLastBindConfig olcOverlay: {2}lastbind olcLastBindPrecision: 60 olcLastBindForwardUpdates: TRUE Does the release 2.5.51 or 2.5.52 could solve this issue ? Regards, -- You are receiving this mail because: You are on the CC list for the issue.

1 11

[Issue 9500] New: back-mdb: index generation failiure
by openldap-its＠openldap.org 06 May '21

06 May '21

https://bugs.openldap.org/show_bug.cgi?id=9500 Issue ID: 9500 Summary: back-mdb: index generation failiure Product: OpenLDAP Version: 2.5 Hardware: All OS: Linux Status: UNCONFIRMED Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: smckinney(a)symas.com Target Milestone: --- Operating system CentOS Linux release 8.3.2011 OpenLDAP version 2.5.2 beta Error adding records. After app. 65539 records. Clientside error: index generation failed Server log: Mar 12 19:17:48 tx01 slapd[30394]: conn=1015 op=4 ADD dn="cn=foo,ou=Roles,ou=RBAC,dc=example,dc=com" Mar 12 19:17:48 tx01 slapd[30394]: slap_get_csn: conn=1015 op=4 generated new csn=20210312191748.484367Z#000000#001#000000 manage=1 Mar 12 19:17:48 tx01 slapd[30394]: slap_queue_csn: queueing 0x7d3d842146e0 20210312191748.484367Z#000000#001#000000 Mar 12 19:17:48 tx01 slapd[30394]: => mdb_idl_insert_keys: c_get hi failed: MDB_NOTFOUND: No matching key/data pair found (-30798) Mar 12 19:17:48 tx01 slapd[30394]: conn=1015 op=4 RESULT tag=105 err=80 qtime=0.000042 etime=0.001244 text=index generation failed Mar 12 19:17:48 tx01 slapd[30394]: slap_graduate_commit_csn: removing 0x7d3d842146e0 20210312191748.484367Z#000000#001#000000 -- You are receiving this mail because: You are on the CC list for the issue.

1 8

[Issue 9461] New: Deletion causes cursor to repeat
by openldap-its＠openldap.org 06 May '21

06 May '21

https://bugs.openldap.org/show_bug.cgi?id=9461 Issue ID: 9461 Summary: Deletion causes cursor to repeat Product: LMDB Version: 0.9.27 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: github(a)nicwatson.org Target Milestone: --- Created attachment 795 --> https://bugs.openldap.org/attachment.cgi?id=795&action=edit repro of cursor delete bug See attached source code for reproduction. The test behaves correctly in 0.9.26 and fails in 0.9.27 and 0.9.28. The failing sequence is: 1. In a dupsort DB, create two different keys and values. 2. Create a cursor, setting the position to the second key. 3. Delete the first key. 4. Have the cursor get the next key. mdb_get_key will return the second key instead of returning MDB_NOT_FOUND. -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9513] New: Enhanced debug output
by openldap-its＠openldap.org 23 Apr '21

23 Apr '21

https://bugs.openldap.org/show_bug.cgi?id=9513 Issue ID: 9513 Summary: Enhanced debug output Product: OpenLDAP Version: 2.5 Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- While debugging ITS#9479 I needed more information on which threads were doing what actions. Also, when looking for delays/hangs/race conditions, the 1-second granularity of the debug msg timestamp was inadequate. And also, some of the debug output for the Search operation was being done in separate Debug calls for a single line of output. This gets jumbled up pretty badly if other threads are printing output as well. New patch set will extend the debug timestamp to have fractional seconds too; it will use clock_gettime for nanosecond resolution if available, otherwise use gettimeofday for microsecond resolution. Also tweak the Search debug output to only use one Debug invocation per line of output. This is MR!279. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 9470] New: Add homedir overlay to core
by openldap-its＠openldap.org 22 Apr '21

22 Apr '21

https://bugs.openldap.org/show_bug.cgi?id=9470 Issue ID: 9470 Summary: Add homedir overlay to core Product: OpenLDAP Version: 2.5 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: overlays Assignee: bugs(a)openldap.org Reporter: quanah(a)openldap.org Target Milestone: --- Symas will contribute its homedir overlay as a core overlay Home directory provisioning overlay The homedir overlay causes slapd to notice changes involving RFC-2307bis style user-objects and make appropriate changes to the local filesystem. This can be performed on both master and replica systems, so it is possible to perform remote home directory provisioning. -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9445] New: ITS#9339/1748ec59a crashes slapd on ip connect in tcpwrappers
by openldap-its＠openldap.org 01 Apr '21

01 Apr '21

https://bugs.openldap.org/show_bug.cgi?id=9445 Issue ID: 9445 Summary: ITS#9339/1748ec59a crashes slapd on ip connect in tcpwrappers Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: grapvar(a)gmail.com Target Milestone: --- When openldap is configured with tcpwrappers, servers/slapd/daemon.c`slap_listener() calls: > hosts_ctl("slapd", dnsname != NULL ? dnsname : SLAP_STRING_UNKNOWN, > peeraddr, ... where `peeraddr' must be client ip addr or literal "unknown" string. Commit [2020-09-06 1748ec59a ITS#9339 Add syncrepl status to cn=monitor] is made so that `peeraddr' contains fixed NULL value. This causes immediate crash of slapd inside tcpwrappers library when client connects using ip protocol at least on Solaris x86-64. I did not verify this on linux, but even if slapd doesn't crash on linux, then tcpwrappers do not work as expected anyway. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 9482] New: slapi_int_get_plugins() may return uninitialized data
by openldap-its＠openldap.org 31 Mar '21

31 Mar '21

https://bugs.openldap.org/show_bug.cgi?id=9482 Issue ID: 9482 Summary: slapi_int_get_plugins() may return uninitialized data Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: grapvar(a)gmail.com Target Milestone: --- ... because > if ( be == NULL ) { > goto done; > } returns before output variable ppFuncPtrs has been initialized. This may be not affect openldap code, but, if I understand correctly, slapi_int_get_plugins() is part of api and may affect 3rd party. -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 9483] New: Need dummy value for AC_TLS_TYPE
by openldap-its＠openldap.org 31 Mar '21

31 Mar '21

https://bugs.openldap.org/show_bug.cgi?id=9483 Issue ID: 9483 Summary: Need dummy value for AC_TLS_TYPE Product: OpenLDAP Version: 2.5 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: build Assignee: bugs(a)openldap.org Reporter: quanah(a)openldap.org Target Milestone: --- If slapd is built without any type of TLS, AC_TLS_TYPE becomes empty, which then causes problems in the test suite. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 9498] New: assert failed in connection_next
by openldap-its＠openldap.org 31 Mar '21

31 Mar '21

https://bugs.openldap.org/show_bug.cgi?id=9498 Issue ID: 9498 Summary: assert failed in connection_next Product: OpenLDAP Version: 2.5 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- Discovered in test074 in CI Thread 5 (Thread 0x7f9767fff700 (LWP 10601)): #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007f9776ba2535 in __GI_abort () at abort.c:79 #2 0x00007f9776ba240f in __assert_fail_base (fmt=0x7f9776d04ee0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55fb742287f0 "c->c_conn_state != SLAP_C_INVALID", file=0x55fb742282cd "connection.c", line=928, function=<optimized out>) at assert.c:92 #3 0x00007f9776bb0102 in __GI___assert_fail (assertion=assertion@entry=0x55fb742287f0 "c->c_conn_state != SLAP_C_INVALID", file=file@entry=0x55fb742282cd "connection.c", line=line@entry=928, function=function@entry=0x55fb74229180 <__PRETTY_FUNCTION__.12455> "connection_next") at assert.c:101 No locals. #4 0x000055fb7418499f in connection_next (c=0x7f9775a7c950, index=0x7f9767ffd82c) at connection.c:928 c_struct = <optimized out> __PRETTY_FUNCTION__ = "connection_next" c_struct = <optimized out> #5 connection_next (c=0x0, index=index@entry=0x7f9767ffd82c) at connection.c:896 __PRETTY_FUNCTION__ = "connection_next" c_struct = <optimized out> #6 0x000055fb742096da in monitor_subsys_rww_update (op=<optimized out>, rs=<optimized out>, e=0x55fb745008d8) at rww.c:194 mi = 0x55fb74299240 <monitor_info> c = <optimized out> connindex = 117 nconns = <optimized out> nwritewaiters = 0 nreadwaiters = 4 i = <optimized out> nrdn = {bv_len = 7, bv_val = 0x55fb74598010 "cn=read,cn=waiters,cn=monitor"} a = <optimized out> buf = "\260\027C`\227\177\000\000\340\211\033`\227\177\000\000x\372O", <incomplete sequence \373> num = 0 len = <optimized out> __PRETTY_FUNCTION__ = "monitor_subsys_rww_update" #7 0x000055fb7420f3df in monitor_entry_update (op=op@entry=0x7f975c2d1280, rs=rs@entry=0x7f9767ffead0, e=e@entry=0x55fb745008d8) at entry.c:59 mi = <optimized out> mp = 0x55fb74598430 rc = 32768 __PRETTY_FUNCTION__ = "monitor_entry_update" #8 0x000055fb74209c2f in monitor_send_children (op=op@entry=0x7f975c2d1280, rs=rs@entry=0x7f9767ffead0, e_nonvolatile=e_nonvolatile@entry=0x55fb745008d8, e_ch=<optimized out>, sub=sub@entry=1) at search.c:103 sub_nv = 0x0 sub_ch = 0x0 mi = 0x55fb74299240 <monitor_info> e = 0x55fb745008d8 e_tmp = <optimized out> mp = <optimized out> rc = <optimized out> nonvolatile = 0 #9 0x000055fb74209cbf in monitor_send_children (op=op@entry=0x7f975c2d1280, rs=rs@entry=0x7f9767ffead0, e_nonvolatile=e_nonvolatile@entry=0x55fb744ff6b8, e_ch=<optimized out>, sub=1) at search.c:139 sub_nv = 0x55fb745008d8 sub_ch = 0x0 mi = 0x55fb74299240 <monitor_info> e = 0x55fb744ffa78 e_tmp = 0x0 mp = <optimized out> rc = <optimized out> nonvolatile = 1 #10 0x000055fb74209f4c in monitor_back_search (op=0x7f975c2d1280, rs=0x7f9767ffead0) at search.c:238 mi = 0x55fb74299240 <monitor_info> rc = <optimized out> e = 0x55fb744ff668 matched = 0x0 e_nv = 0x55fb744ff6b8 e_ch = 0x0 mask = 4159 #11 0x000055fb74186121 in fe_op_search (op=0x7f975c2d1280, rs=0x7f9767ffead0) at search.c:406 bd = 0x55fb74298880 <slap_frontendDB> #12 0x000055fb74185b24 in do_search (op=0x7f975c2d1280, rs=0x7f9767ffead0) at search.c:247 base = {bv_len = 10, bv_val = 0x7f975c2d1248 "cn=Monitor"} siz = 0 off = 0 i = <optimized out> #13 0x000055fb74183504 in connection_operation (ctx=0x7f9767ffebb0, arg_v=0x7f975c2d1280) at connection.c:1168 -- You are receiving this mail because: You are on the CC list for the issue.

1 5

[Issue 9479] New: asyncmeta: test074 failure to terminate
by openldap-its＠openldap.org 31 Mar '21

31 Mar '21

https://bugs.openldap.org/show_bug.cgi?id=9479 Issue ID: 9479 Summary: asyncmeta: test074 failure to terminate Product: OpenLDAP Version: 2.5 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: backends Assignee: bugs(a)openldap.org Reporter: quanah(a)openldap.org Target Milestone: --- When the asyncmeta backend is enabled in master test074 routinely fails to complete, causing CI/CD to force kill the container and marking the branch as failed. This same problem with test074 has manifested in environments outside of the CI/CD system, such as the launchpad PPA service. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

← Newer
1
...
5
6
7
8
9
10
11
...
32
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs March 2021